ci: refactor unit test workflow

[Flouse]

What this PR does / why we need it?

• This PR follows ci: refactor cargo build and cargo clippy workflow #1350.
  Try to make CIs simpler, triggered automatically.

What is the impact of this PR?

• No Breaking Change
• With cache, cargo clippy takes only 5 minutes.
• With cache, cargo test takes only 7 minutes.

CI Settings

CI Usage

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

CI Switch

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

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

[yangby-cryptape]

The CI scripts are fine, their failure due to bugs.

The "metadata-test" in the latest 3 commits are all failed on current default branch.

In current default branch, the "metadata-test" has a 100% chance to fail, "v3-core-test" is 80%.

[KaoImin]

The CI scripts are fine, their failure due to bugs.

The "metadata-test" in the latest 3 commits are all failed on current default branch.

In current default branch, the "metadata-test" has a 100% chance to fail, "v3-core-test" is 80%.

The metadata-test written in js is outdated and has been removed in #1355.

[yangby-cryptape]

No space left on device

Limit is 14 GB of SSD space.

My suggestions:

• Execute cargo clean if the size of the disk is bigger than 10 GB.
• cargo sweep --maxsize 8192
  • Binaries can be downloaded directly.