replace rkyv with custom serde

[hero78119]

Follow up on #1171
replace rkyv with custom serde for 2 reasons

• serialization to bytes need to implement rkyv friendly struct, or leverage external library, e.g. "rkyv + bincode". rkyv friendly struct is not friendly for existing application in particular struct are defined in 3rd-party library. Thus previously we integrate bincode for the serialiation to bytes. This bring extra effort for guest program as we need bincode to deserialize back to owned struct.
• in deserialize rkyv will access high addr to retrieve some meta information before sequential read. Below are example read pattern

hint address 28000004
hint address 28000008
hint address 280c8770 <- high addr accessed to fetch meta data
hint address 280c876c
hint address 280c876c
hint address 280c8770
hint address 28000010
hint address 28000010
hint address 28000010
hint address 28000010
hint address 28000014
hint address 28000014
hint address 28000014
...

The high order access not friendly if we want to record max accessed address in each shard for memory region initialized across shard.

New ceno_serde crates credits to https://github.com/openvm-org/openvm/tree/main/crates/toolchain/openvm/src/serde

benchmark

Run on 23817600 with K=6, cache trace = none, 1x4090

Component	base Time	Init-Across-Shard Time	Custom Serde Time	Init-Across-Shard Improvement	Custom Serde Improvement
app.prove	203 s	175 s	160 s	↓ 13.8%	↓ 21.2%
emulator.preflight-execute	43.9 s	35.8 s	36.6 s	↓ 18.5%	↓ 16.6%
app_prove.inner	158 s	139 s	123 s	↓ 12.0%	↓ 22.2%
create_proof_of_shard (shard_id = 0)	14.9 s	4.91 s	8.46 s	↓ 67.0%	↓ 43.2%
create_proof_of_shard (shard_id = 1)	16.4 s	12.7 s	3.74 s	↓ 22.6%	↓ 77.2%

Overall cycle 322620252 -> 315955342 (2.06%)

Custom Serde updated setting: max cell: (1 << 30) * 8 / 4 / 2 ------> (1 << 30) * 10 / 4 / 2
keccak blowup K=6 unchange

[kunxian-xia]

LGTM except one minor issue.

[kunxian-xia]

nitpick: add a link to the function finalize() in ceno_host/src/lib.rs so that whenever we make any change here, we won't forget to reflect it there.