Adding benchmark test - root/child chain measurements

[stana-miric]

Description

This PR includes adding benchmark test for testing tx execution on root and child chain. Also, benchmark-test command is added for the purpose of testing on a test environment were we have both root and child chain running. The changes includes:

1. Adding benchmark directory that includes tests and helpers for tests.

• helpers.go that has helper functions needed in tests like deploying contracts and similar,
• root_child_benchmark_test.go tests execution of tx by calling the node on both root and child chain
• transition_benchmark_test.go tests calling contracts on transition instance. This test uses SampleContract which is taken from go-ethereum test since we want to compare execution on both edge and geth

2. Adding benchmark-test command(which tests the same thing as root_child_benchmark_test): the command has rootJSONRPC, childJSONRPC, startCluster and privateKey flags. If startCluster is false, then the local cluster will not be started and the provided addresses will be used as the endpoints to the root and child chains. If startCluster is set to true, the local cluster will be started automatically. If the private key is specified, it will be used as the transaction sender. Otherwise, the local cluster will generate a sender key. If startCluster is set to false, then the sender must have enough funds for sending transactions.. Example how to run the command:
   polygon-edge benchmark-test --childJSONRPC="http://127.0.0.1:12001" --rootJSONRPC="http://127.0.0.1:8545" --privateKey="aa75e9a7d427efc732f8e4f1a5b7646adcc61fd5bae40f80d13c8419c9f43d6d"
   or
   polygon-edge benchmark-test --startCluster
3. There are changes in e2e testing framework which replaces testing.T with testing.TB interface in order to use some functionality in the benchmark tests as well
4. tx relayer exposes WaitForReceipt and SumbitTransaction

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

[vcastellm]

Let's talk about this