Marinade common CLI artifacts

[ochaloup]

I consider this repository to be common to any liquid staking program CLI in Rust.

The idea is to work solely with Anchor Client and the RequestBuilder.
Unfortunately, I fight a bit with the builder and I haven't fight a way through to append other transactions than the one the builder crates.
Maybe it would be option to use Transaction instead of the builder but I haven't found a fine way how to merge transactions either. To use a single "thing" I decided to work with the RequestBuilder. But there could be something nicer that I haven't been able to find.

I decided to work with the RpcMarinade as it seems to an easy wrapper around client and anchor stuff that can be used within the CLI program. The methods like validator_list,... are listed as functions but wrapped inside of the rpc marinade for an easier use.

[ochaloup]

@aankor I moved a part of CLI arguments, those that seems to be common to other CLI, here. My intention is to not copy&paste declaration.

(I use workspace intentionally here while it could be you have some better idea on module split.)

[ochaloup]

From discussions with @aankor, the following should be adjusted:

• DynSigner should be in a separate crate (+ PR to Anchor [code should be created](DynSigner struct: for Solana CLI usage to wrap Box<dyn Signer> to align with Client<C> coral-xyz/anchor#2550 to check possibility to have that there)
• remove all the rpc client helper stuff retrying is wrong (cron job rerun will manage it), remove checks for mint/token
• place execution log handling to separate method like log_execution
  • use error! on error, debug! for log messages on success
• consider not using specialized method for execution and move that logic under the particular CLI repo, having the call looks like txes.map(|tx| log_execution(tx.execute())) (need to be considered, not clear about this now)
  • when specialized method is used then not working with vec but use iterable
• simulate can properly works only with one transaction