Update to EVM Pectra hard-fork

[m-Peter]

Work towards: onflow/flow-go#7152

Description

Changes related to EVM Pectra hard-fork.

---

For contributor use:

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the standards mentioned here.
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

Summary by CodeRabbit

• New Features

  • Added support for EIP-7702 transactions, including contract write and self-execution flows.
  • Expanded special block number handling to include earliest, safe, finalized, latest, and pending states.
  • Enhanced transaction argument structure to support new transaction types and fields.
  • Introduced chain configuration injection for improved tracing and debugging.

• Bug Fixes

  • Standardized block number resolution and improved handling of special block tags.
  • Corrected bloom filter computation for blocks and receipts.
  • Fixed block override key naming for accurate debug trace calls.

• Dependency Updates

  • Upgraded Go toolchain and multiple direct and indirect dependencies for improved stability and compatibility.

• Tests

  • Introduced comprehensive tests for EIP-7702, Pectra upgrade, and contract interactions using Viem and Web3.js.
  • Updated test expectations and added new scenarios for advanced transaction and contract features.

• Chores

  • Added new Solidity contract and configuration files for testing and client integration.

[zhangchiqing]

Optional, I would suggest to use -10 instead of -5, in case we need to define other BlockNumber.

[m-Peter]

We don't define this special value, this is actually defined from Geth itself. See here: https://github.com/onflow/go-ethereum/blob/master/rpc/types.go#L66 . By using -10 we would deviate from Geth, and I want to avoid that.

[zhangchiqing]

Suggested change

	} else if blockNumber <= rpc.PendingBlockNumber {
	} else if blockNumber < 0 {

Optional, but I think this would be slightly safer.

[m-Peter]

I have updated the implementation in this commit: c95ea08, to make it more explicit and readable. I want to avoid using magic values like 0, I would prefer making comparisons with the constants defined by Geth.