Port `MessageTrace` and `VMTracer` machinery from Hardhat

Part of https://github.com/NomicFoundation/edr/issues/246

While this is not immediately at the top of the module dependency chain, the logic was pretty self-contained (so easier to port and verify) and it was helpful for me to port the important trace data types as it helped me understand how the information flows and what's used and how.

The biggest change is that this exposes a single observe method that can be used in HH to digest the traces directly on the Rust side, rather than 3 separate methods, without marshalling the data over FFI when fetching the stack trace (and possibly in the future if we remove the minimal node/vm EthereumJS events).

The companion branch is here https://github.com/NomicFoundation/hardhat/tree/refactor/port-vm-tracer; I still need to figure out how to streamline the process and at least prove that the PR works in a backwards-compatible fashion with Hardhat.

It might be helpful to see these files used when porting, when reviewing:

https://github.com/NomicFoundation/hardhat/blob/main/packages/hardhat-core/src/internal/hardhat-network/stack-traces/message-trace.ts
https://github.com/NomicFoundation/hardhat/blob/main/packages/hardhat-core/src/internal/hardhat-network/stack-traces/vm-tracer.ts
https://github.com/NomicFoundation/hardhat/blob/main/packages/hardhat-core/src/internal/hardhat-network/provider/vm/exit.ts

NomicFoundation / edr

Port `MessageTrace` and `VMTracer` machinery from Hardhat #531

⚠️ No Changeset found