test: check genesis data of dev chain in unit tests to lock the consensus

[yangby-cryptape]

What this PR does / why we need it:

This PR add a unit test to check genesis data of dev chain to lock the consensus.

Then, some simple break changes could be exposed in CI tests.

⚠️ Known Issues:

• Although, after refactor(executor): thread local instead of global variable #1280, the system contract could be reload, but it is still a global variable, so it doesn't support multi-threads.

  So, one crate could ONLY have ONE unit test which uses AxonExecutor.

Which toolchain this PR adaption:

No Breaking Change

Special notes for your reviewer:

NIL

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