Add a flag to deploy command for stake manager address

[goran-ethernal]

Description

Added a --stake-manager flag to deploy command which deploys rootchain contracts, which holds the address of the StakeManager contract on rootchain.

Given flag is mandatory, so the StakeManager contract has to be deployed already on the rootchain. This is needed since StakeManager is a single instance contract on rootchain so it should be deployed only once.

To help deployers, we provided a command that only deploys StakeManager contract. It is called stake-manager-deploy.
It has these flags:

• data-dir - specifies the directory for the Polygon Edge data if the local FS is used.
• config - the path to the SecretsManager config file, if omitted, the local FS secrets manager is used.
• private-key - hex-encoded private key of the account which executes rootchain commands.
• genesis - genesis file path, which contains chain configuration.
• stake-token - address of ERC20 token used for staking on rootchain.
• test - indicates if command is run in test mode. If test mode is used contract will be deployed using test account and a test stake ERC20 token will be deployed to be used for staking.

Flags data-dir and config are mutually exclusive.
Flag private-key is mutually exclusive with data-dir and config flags.
So if the StakeManager deployer doesn't have secrets initialized, then he would need to use the private-key flag.

Flag test is mutually exclusive with data-dir, config, private-key and stake-token flags, and is only used for testing purposes, since when this flag is on, test account will be used to deploy StakeManager and a mock ERC20 token will be deployed and used for staking.

If test is not used (in case when deploying StakeManager to let's say Mumbai main net), then deployer will need to provide the address to the token that was deployed on root that will be used for staking (in this case Matic).

stake-manager-deploy command will update the genesis file and save the StakeManager and StakeToken addresses to the Bridge config in genesis.json.

To summarize the flow of deploying supernet would be:

1. Initialize secrets for each validator.
2. Execute genesis command.
3. Deploy StakeManager contract if it is not already deployed to the rootchain.
4. Execute rootchain deploy command (provide StakeManager address to it).
5. Whitelist validators (SupernetManager deployer must do it).
6. Register validators (each validator for itself).
7. Do initial staking (each validator for itself).
8. Finalize genesis on SupernetManager (SupernetManager deployer must do it).

The PR also changes name of the --native-root-token flag in fund and stake commands to better picture which token is in question. So the --native-root-token flag in those commands is renamed to --stake-token.

Tagging @DannyS03 to update the docs.

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]

As we mentioned, this need to be mandatory instead of optional and add a new SM deploy command.