fix: use a same trie for the same chain

[yangby-cryptape]

What this PR does / why we need it?

Currently, during axon starting, there will be 4 RocksTrieDB instances are used.
This PR only reduce the number of instances from 4 to 1.

Description

Each time to create a new instance of RocksTrieDB, a new cache will be created:

axon/core/executor/src/adapter/trie/db.rs

Lines 148 to 150 in fc199ba

	pub fn new_evm(db: Arc<DB>, cache_size: usize) -> Self {
	Self::new(db, StateStorageCategory::EvmState, cache_size)
	}

axon/core/executor/src/adapter/trie/db.rs

Lines 29 to 34 in fc199ba

	pub struct RocksTrieDB {
	db: Arc<DB>,
	category: StateStorageCategory,
	cache: RwLock<HashMap<Vec<u8>, Vec<u8>>>,
	cache_size: usize,
	}

Different cache for different instances, then the RwLock can do nothing for consistency.

⚠️ This PR doesn't resolve the issue completely, it just avoids the issue when starts.

What is the impact of this PR?

No Breaking Change

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