pallet_revive: support uploading EVM bytecode via upload_code

[marian-radu]

Fixes paritytech/contract-issues#182

Add support for EVM bytecode to the upload_code extrinsic. Tests in issue paritytech/contract-issues#182 send hardhat_setCode, which uses revive's upload_code API; this change makes that flow accept and store EVM bytecode.

Add a unit test that validates the new behavior.

Note: This PR targets the anp-dirty-node branch.

[pgherveou]

Do we need to upload EVM bytecode, the runtime code is always stored on chain after deployment, and it does not reference child contracts by hash but by the bytecode so we should not need to pre-deploy any contract code?

[marian-radu]

@pgherveou
After analyzing the test setup further, I noticed that hardhat_setCode is used to meet the SeiNativeOracleAdapter contract’s expectation that the SeiNativeOracle code be loaded at a specific address.

1. Test setup uploads SeiNativeOracle at ORACLE_PRECOMPILE_ADDRESS
   https://github.com/paritytech/scc-testing/blob/main/dragonswap-sei-native-oracle-adapter/test/SeiNativeOracleAdapter.test.js#L30

2. SeiNativeOracleAdapter expects SeiNativeOracle to be loaded at ORACLE_PRECOMPILE_ADDRESS.
   https://github.com/dragonswap-app/sei-native-oracle-adapter/blob/master/src/SeiNativeOracleAdapter.sol#L15

@smiasojed recently opened a PR that adds similar functionality at the Pallet Revive API level. After a quick sync-up with him this morning, we concluded that it will be useful to merge both PRs into master.
#10129

hardhat_setCode documentation:
https://v2.hardhat.org/hardhat-network/docs/reference#hardhat_setcode