Introduce Weight v2 support for EVM (frontier)

[tgmichel]

What does it do?

This PR introduces support for external cost recording in evm execution.

The goal is to add additional metric(s) capacity that will result in an OutOfGas when exhausted. When the evm is compiled with a with-substrate feature, adds two additional PrecompileHandle methods - record_external_cost and refund_external_cost - which are called on pre_validate, that is, before an OpCode is executed. This way we make sure each OpCode can be executed not only taking native remaining gas into consideration, but also any other metric that the execution is bounded with. In the case of Moonbeam there is only one metric for now - pov_size - but it will also support ref_time soon™. This keeps behavioural changes in the evm to bare minimum while adding the virtual gasometer dimension in the Substrate backend.

Runtime Changes

• Switch to shanghai configuration.
• External cost recording. Introduces a new capacity based on GasLimitPovRatio, which is set to 1/4 - 4 gas unit per byte.
• Adapt all precompiles to record pov cost associated with storage read operations in addition to gas cost.
• Ethereum call runtime api now supports external cost recording in non-transactional context as well.

Client Changes

• New ethereum-block based notification. Pubsub previsouly reacted to substrate import notification stream for NewHeads subscriptions. This caused race-conditions, because that is the channel also used by the secondary db mapper. Now pubsub will emit to subscribers only when the secondary db has effectively mapped the ethereum block.

⚠️ Breaking Changes ⚠️

The concept of OutOfGas and refunds is expanded, and might break some Dapp asumptions.

OutOfGas can now be thrown transaction-wide if any of the configured metrics' capacity is reached - in other words, the evm can OOG with remaining legacy gas in the gasometer.

Refunds are based on the more consumed resource after the execution - in other words, if more pov_size has been consumed proportionally than legacy gas, the refund will be calculated using pov_size.

[github-actions]

Coverage generated "Tue Jun 6 10:52:23 UTC 2023":
https://s3.amazonaws.com/moonbeam-coverage/pulls/2316/html/index.html

Master coverage: 71.19%
Pull coverage: 71.17%

[librelois]

I lelft some comments, there is also some TODO that should be fixed before merge

[tgmichel]

I lelft some comments, there is also some TODO that should be fixed before merge

thank you @librelois , done

[nbaztec]

A question about the channel, if this is created per-subscription is it possible to OOM kill the client via flooding it with subscriptions?

[tgmichel]

If the connection is kept open in the client end, the limit of channels is the number of websocket connections the server supports. Each time a new ethereum block is produced, channels associated to closed connections are removed from the pool.