Sanity check tests

[goran-ethernal]

Description

This PR adds sanity check framework to blade with some sanity check tests, that can be run on a specified network (testnet).

The PR also adds a command to blade, which can be used to run sanity check tests:

Runs a sanity check tests on a specified network

Usage:
   sanity-check [flags]

Flags:
      --epoch-size uint             epoch size on the network for which the sanity check is run (default 10)
  -h, --help                        help for sanity-check
      --jsonrpc string              the JSON-RPC interface (default "http://0.0.0.0:8545")
      --mnemonic string             the mnemonic used to fund accounts if needed for the sanity check
      --receipts-timeout duration   the timeout for waiting for transaction receipts (default 30s)
      --to-json                     saves results to JSON file
      --validator-keys strings      private keys of validators on the network for which the sanity check is run

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

Tests added through this PR

1. Stake test for validator
2. Unstake test for validator
3. Register a new validator with stake
4. Withdraw validator rewards test.
5. Unstake all (remove validator) test.

To run tests locally on your machine, follow these steps:

1. Run this command from blade repo:

./scripts/cluster polybft

2. In blade repo, you will see folders like test-chain-1, test-chain-2, test-chain-3, test-chain-4. Inside each of them, collect private keys located in files consensus/validator.key. You will need them for the --validator-keys flag.
3. Run sanity-check command:

./blade sanity-check --mnemonic "code code code code code code code code code code code quality" --jsonrpc "http://localhost:10002" --receipts-timeout 2m --validator-keys [list of keys from previous step separated by a coma]

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