refactor: evmbin: CLI flag for coloured log levels. CLI flag for output to log file

[ltfschoen]

Extension of PR #10657.
Not to be merged prior to #10657 and #10742

• Temporarily added evmbin/res/create2callPrecompiles.json and evmbin/res/teststate.json just as input files for testing the code with CLI commands
• Use fern crate for log level colours
• Add CLI flag --logging to choose log level (consistent with parity-ethereum CLI)
• Add CLI flag --logging-to-file to save outputs to output.log
• Restrict use of logging levels in production (i.e. cargo build -p evmbin --release) to info! in Cargo.toml. In development users may use debug! or trace!.
• Question 1 I made changes that to std_json.rs to add colours and log levels, but the tests failed so I reverted the changes in commit a687150. Were those changes on the right track?
  ANS: Note that we cannot convert writing to the stdout buffer with writeln! in std_json.rs to writing directly to stdout by use of macros with color like info!. See the module doc comments in std_json.rs

The changes may be tested as follows:

std-json

cargo build -p evmbin --release;
./target/release/parity-evm state-test ./evmbin/res/create2callPrecompiles.json --only create2callPrecompiles --chain Constantinople --logging 2 --std-json --std-dump-json

json

cargo build -p evmbin --release;
./target/release/parity-evm state-test ./evmbin/res/create2callPrecompiles.json --only create2callPrecompiles --chain Constantinople --logging 2 --json

output to a file output.log

cargo build -p evmbin --release;
./target/release/parity-evm state-test ./evmbin/res/create2callPrecompiles.json --only create2callPrecompiles --chain Constantinople --logging 2 --json --logging-to-file

[parity-cla-bot]

It looks like @ltfschoen signed our Contributor License Agreement. 👍

Many thanks,

Parity Technologies CLA Bot

[ordian]

closing as stale