[evm-tracing-1] runtime level implementation

[dmitrylavrenov]

No description provided.

[Copilot]

Pull Request Overview

This PR integrates EVM debug tracing support at the runtime level by adding new modules, runtime APIs, and event propagation for EVM, gasometer, and runtime events. Key changes include updates to feature definitions (adding new tracing modules), the implementation of a new runtime interface for EVM tracing in primitives-evm-tracing-ext, and modifications in humanode-runtime to integrate and expose the evm-debug-api functionalities.

Reviewed Changes

Copilot reviewed 14 out of 15 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
utils/checks/snapshots/features.yaml	Added new feature entries for evm-debug-api, primitives-evm-tracing-events, and primitives-evm-tracing-ext.
crates/primitives-evm-tracing-ext/src/lib.rs	Introduced the EvmTracingExt trait with host function wrappers for decoding and emitting EVM events.
crates/primitives-evm-tracing-events/*	Added event definitions and conversion functions for EVM events, gasometer events, and runtime events.
crates/humanode-runtime/src/lib.rs	Integrated EVM tracing into runtime APIs (trace_transaction, trace_block, trace_call).
crates/humanode-runtime/src/evm_tracer.rs	Implemented the EvmTracer that sets up event listener proxies and calls corresponding host functions.
Remaining Cargo.toml files	Updated dependencies and feature flags to support the new EVM tracing functionality.
crates/evm-debug-api/*	Exposed the runtime API for the EVM debug logic using sp_api.

Comments suppressed due to low confidence (1)

crates/humanode-runtime/src/lib.rs:1518

• The new EVM tracing integration in the extrinsics loop lacks explicit test coverage. Consider adding unit or integration tests to verify that EVM transactions and non-Ethereum extrinsics are traced correctly.

                    RuntimeCall::Ethereum(transact { transaction }) => {

[MOZGIII]

I'm up-to-date with the changes here; ping me please when the rest of the comments are resolved

[MOZGIII]

Looks good with the exception of the features confusion - if we address that we'd be good to go imo