Fix block import error for EVM node client

[wangminqi]

This is referring to polkadot-evm/frontier#603

[linear]

P-262 Runtime upgrade simulation fails to work

See:

https://github.com/litentry/litentry-parachain/actions/runs/6909835415

https://github.com/litentry/litentry-parachain/actions/runs/6912731426

We haven' used it for a long time, there might be multiple problems here:

1. the wget downloading doesn't work for an unpublished release
2. polkadot/util-crypto can't be found
3. the forked parachain network can't be started with scraped rococo state:

2023-11-18 08:57:30.021  INFO tokio-runtime-worker sc_basic_authorship::basic_authorship: [Parachain] 🙌 Starting consensus session on top of parent 0xfa34eacb0179181f8518c87174346f3733831a2f056aaeaa13f9b611ab7d1c71
2023-11-18 08:57:30.021  INFO tokio-runtime-worker runtime::frame-support: [Parachain] ⚠️ ParachainSystem declares internal migrations (which *might* execute). On-chain `StorageVersion(2)` vs current storage version `StorageVersion(2)`
2023-11-18 08:57:30.021  INFO tokio-runtime-worker runtime::frame-support: [Parachain] ⚠️ XcmpQueue declares internal migrations (which *might* execute). On-chain `StorageVersion(3)` vs current storage version `StorageVersion(2)`
2023-11-18 08:57:30.021  INFO tokio-runtime-worker runtime::frame-support: [Parachain] ⚠️ PolkadotXcm declares internal migrations (which *might* execute). On-chain `StorageVersion(0)` vs current storage version `StorageVersion(1)`
2023-11-18 08:57:30.021  INFO tokio-runtime-worker runtime::frame-support: [Parachain] ⚠️ DmpQueue declares internal migrations (which *might* execute). On-chain `StorageVersion(2)` vs current storage version `StorageVersion(1)`
2023-11-18 08:57:30.023 DEBUG tokio-runtime-worker sc_basic_authorship::basic_authorship: [Parachain] Attempting to push transactions from the pool.
2023-11-18 08:57:30.023 DEBUG tokio-runtime-worker sc_basic_authorship::basic_authorship: [Parachain] Pool status: PoolStatus { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 }
2023-11-18 08:57:30.023  INFO tokio-runtime-worker sc_basic_authorship::basic_authorship: [Parachain] 🎁 Prepared block for proposing at 1 (0 ms) [hash: 0xdc3f79180bd2a6a0d07d8debec581c161483bb495dd85bcd8d6f4417e1e180ed; parent_hash: 0xfa34…1c71; extrinsics (2): [0xa3b7…5d44, 0x21ac…48d1]]
2023-11-18 08:57:30.025  INFO tokio-runtime-worker aura: [Parachain] 🔖 Pre-sealed block for proposal at 1. Hash now 0xafb8eb15fbdf5d72649bf7f9fbbcc2af16356aac21a23308faabf8f349836bad, previously 0xdc3f79180bd2a6a0d07d8debec581c161483bb495dd85bcd8d6f4417e1e180ed.
2023-11-18 08:57:30.025  WARN tokio-runtime-worker aura: [Parachain] Error with block built on 0xfa34eacb0179181f8518c87174346f3733831a2f056aaeaa13f9b611ab7d1c71: Import failed: Runtime Ethereum block not found, rejecting!
2023-11-18 08:57:30.025  INFO tokio-runtime-worker cumulus-collator: [Parachain] PoV size { header: 0.1787109375kb, extrinsics: 2.7275390625kb, storage_proof: 5.8515625kb }
2023-11-18 08:57:30.026  INFO tokio-runtime-worker cumulus-collator: [Parachain] Compressed PoV size: 7.9921875kb
2023-11-18 08:57:30.026 ERROR tokio-runtime-worker cumulus-collator: [Parachain] Failed to collect collation info. error=UnknownBlock("Header was not found in the database: 0xafb8eb15fbdf5d72649bf7f9fbbcc2af16356aac21a23308faabf8f349836bad")

4. error when running runtime upgrade:

RpcError: 1010: Invalid Transaction: Inability to pay some fees , e.g. account balance too low

[wangminqi]

The sync issue "Runtime Ethereum block not found, rejecting!" is now recovered.
The client side needs to upgrade first since we introduce new HostFunction.

[Kailai-Wang]

Looks good, thanks.

Tested OK locally.