Load test runner implementation

[goran-ethernal]

Description

GO implementation of a load test runner.

Load test tool can be run on the blade binary, since it is added as a command in blade:

Runs a load test on a specified network

Usage:
   load-test [flags]

Flags:
      --dynamic                     indicates whether the load test should generate dynamic transactions
  -h, --help                        help for load-test
      --jsonrpc string              the JSON-RPC interface (default "http://0.0.0.0:8545")
      --mnemonic string             the mnemonic used to generate and fund virtual users
      --name string                 the name of the load test (default "load test")
      --receipts-timeout duration   the timeout for waiting for transaction receipts (default 30s)
      --to-json                     saves results to JSON file
      --txpool-timeout duration     the timeout for waiting for the transaction pool to empty (default 10m0s)
      --txs-per-user int            the number of transactions per virtual user (default 1)
      --type string                 the type of load test to run (supported types: eoa, erc20, erc721) (default "eoa")
      --vus int                     the number of virtual users (default 1)
      --wait-txpool                 waits for tx pool to empty before collecting results

Global Flags:
      --json   get all outputs in json format (default false)

How to run:

1. Run the cluster of n validators.

2. Build the binary:

make build

3. Run load-test command on blade binary:

./blade load-test --mnemonic "code code code code code code code code code code code quality" --jsonrpc "http://localhost:50002" --name "My Test" --type ERC20 --vus 10 --txs-per-user 1000

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have updated the official documentation
• I have added sufficient documentation in code

Testing

• I have tested this code with the official test suite
• I have tested this code manually