feat(cli): Add CLI for chain deployment and config

[jmalicevic]

We do not want to deploy the chain using makefiles.

Startup/ config/ stopping

For CLI inspiration, we can look at Malachite but we should be able to run a command of the form:

start -n 4 -v 3 --path-to-config

The config can have configuration parameters for what we want , for example:

• path to jwt secret,
• path to p2p key
• reth configuration parameters that should be read and passed on to reth in the compose file

The chain should also be stoppable via a command of the form.
stop

We should also be able to stop individual nodes.

stop --node-id X

Contract deployment and key generation

We should also be able to deploy a contract to the chain based on where it is launched:

• deploy contract_name signing_key

We will also need to generate keys we can use locally (either via anvil and have them stored somewhere but reused in the above command).

Optionally, logs should be retrievable as well via a log command.

DoD

• CLI that can be used instead of the makefile.
• Documentation describing the available commands and their parameters.
• Documentation describing the config. (ref [EPIC] Documentation #73 )

[sryps]

Just to confirm, this will need to launch reth as well, so just have a check in place that the bin is available and start it with this command?

[jmalicevic]

Yes it should launch reth too.

ALso, another thing is parametrizing the number of nodes (including reth nodes). So the reth deployment might need to be altered, or we'll need a script to put in a compose.yaml file the correct ports based on node number and the cli flags based on a config.

#91