feat(cli): check user provided genesis if not first run

[yangby-cryptape]

What this PR does / why we need it:

This PR add a feature that:

• Check user provided genesis if not first run (ref: The executable binary still can run normally even the genesis state is changed. #1275).

  • Also check if the genesis state is changed.

And this PR fixes a potential issue:

• If it's not the first run, the genesis in Axon struct is incorrect.

  • Because the state_root and receipts_root will be set to the correct values only when it is the first run.

    • They are set in the method execute_transactions(..):

      axon/core/run/src/lib.rs

      Lines 206 to 207 in 1f34617

      	self.genesis.block.header.state_root = self.state_root;
      	self.genesis.block.header.receipts_root = resp.receipt_root;

    • But if it's not first run, execute_transactions(..) will not be called.

      axon/core/run/src/lib.rs

      Lines 127 to 131 in 1f34617

      	match storage.get_latest_block(Context::new()).await {
      	Ok(_) => {
      	log::info!("The Genesis block has been initialized.");
      	return Ok(());
      	}

      
      

      axon/core/run/src/lib.rs

      Line 149 in 1f34617

      self.execute_transactions(&mut mpt, &trie_db, &storage)

  This is not a bug currently, because these fields are not used.

Which issue(s) this PR fixes:

Fixes #1275.

Which toolchain this PR adaption:

No Breaking Change

Special notes for your reviewer:

Since it has to run a temporary empty chain to generate the genesis state, so it uses temporary directories to create RocksAdapter and RocksTrieDB.

But system_contract::init(..) sets a global environment variable, so it has to be called with the real path.

I am not sure whether it OK or not:

• Could system_contract::init(..) be called twice?
• Is system_contract::init(..) sensitive with the height?
  Because the first time it is called, the height will always be 0 after this PR.

CI Description

CI Name	Description
Chaos CI	Test the liveness and robustness of Axon under terrible network condition
Cargo Clippy	Run cargo clippy --all --all-targets --all-features
Coverage Test	Get the unit test coverage report
E2E Test	Run end-to-end test to check interfaces
Code Format	Run cargo +nightly fmt --all -- --check and cargo sort -gwc
Web3 Compatible Test	Test the Web3 compatibility of Axon
v3 Core Test	Run the compatibility tests provided by Uniswap V3
OCT 1-5 | 6-10 | 11 | 12-15 | 16-19	Run the compatibility tests provided by OpenZeppelin

CI Usage

Check the CI you want to run below, and then comment /run-ci.

CI Switch

• Chaos CI
• Cargo Clippy
• Coverage Test
• E2E Tests
• Code Format
• Unit Tests
• Web3 Compatible Tests
• OCT 1-5 And 12-15
• OCT 6-10
• OCT 11
• OCT 16-19
• v3 Core Tests