refactor!: insert metadata directly and remove genesis transactions

[KaoImin]

What this PR does / why we need it?

This PR removes the generation of genesis transactions. The first two metadata and the consensus config are inserted to DB directly.

What is the impact of this PR?

No Breaking Change

PR relation:

• Ref #

CI Settings

CI Usage

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

CI Switch

• 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
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

[Flouse]

Now the following code is useless, right?

axon/core/run/src/tests.rs

Lines 130 to 147 in f000c0f

	for (i, (block_cached, tx)) in genesis
	.block
	.tx_hashes
	.iter()
	.zip(genesis.txs.iter())
	.enumerate()
	{
	let tx_cached = tx.transaction.hash;
	assert_eq!(
	*block_cached, tx_cached,
	"check hash of tx[{i}], in-block: {block_cached:#x}, tx-cached: {tx_cached:#x}",
	);
	let calculated = tx.transaction.clone().calc_hash().hash;
	assert_eq!(
	tx_cached, calculated,
	"check hash of tx[{i}], cached: {tx_cached:#x}, calculated: {calculated:#x}",
	);
	}

[KaoImin]

Now the following code is useless, right?

axon/core/run/src/tests.rs

Lines 130 to 147 in f000c0f

	for (i, (block_cached, tx)) in genesis
	.block
	.tx_hashes
	.iter()
	.zip(genesis.txs.iter())
	.enumerate()
	{
	let tx_cached = tx.transaction.hash;
	assert_eq!(
	*block_cached, tx_cached,
	"check hash of tx[{i}], in-block: {block_cached:#x}, tx-cached: {tx_cached:#x}",
	);
	let calculated = tx.transaction.clone().calc_hash().hash;
	assert_eq!(
	tx_cached, calculated,
	"check hash of tx[{i}], cached: {tx_cached:#x}, calculated: {calculated:#x}",
	);
	}

Yes

[Flouse]

/run-ci

[github-actions]

CI tests run on commit:

• commit id: 7d73ca2

CI test list:

• OCT 1-5 And 12-15
• OCT 6-10
• OCT 11
• OCT 16-19
• v3 Core Tests
• Web3 Compatible Tests

Please check ci test results later.