Add essential EIP-7756 tracing fields

[shemnon]

Add (for eof) section and funcion depth fields, and make pc container relative instead of code section relative.

[shemnon]

This was causing the depth field to read incorrectly when this case triggered. Not sure if here was any way to leverage it. Also, EOF only.

[rakita]

Good find! Yeah it is good fix and it is EOF only

[codspeed-hq]

CodSpeed Performance Report

Merging #2023 will improve performances by 4.6%

_{Comparing shemnon:eof/tracing (21de630) with main (a8f9824)}

Summary

⚡ 1 improvements
✅ 7 untouched benchmarks

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
⚡	precompile bench | ecrecover precompile	201.8 µs	192.9 µs	+4.6%

[rakita]

I have already made a change so current pc is doing the same thing as trace_pc

revm/crates/interpreter/src/interpreter/ext_bytecode.rs

Lines 87 to 95 in be92e1d

	fn pc(&self) -> usize {
	// SAFETY: `instruction_pointer` should be at an offset from the start of the bytecode.
	// In practice this is always true unless a caller modifies the `instruction_pointer` field manually.
	unsafe {
	self.instruction_pointer
	.offset_from(self.base.bytecode().as_ptr()) as usize
	}
	}
	}

and bytecode() gives self.base.eof().raw here:

revm/crates/bytecode/src/bytecode.rs

Lines 137 to 143 in be92e1d

	pub fn bytecode(&self) -> &Bytes {
	match self {
	Self::LegacyAnalyzed(analyzed) => analyzed.bytecode(),
	Self::Eof(eof) => &eof.body.code,
	Self::Eip7702(code) => code.raw(),
	}
	}

[rakita]

Okay my mistake, will see to change the fn pc to become trace_pc it is not used in any other place for EOF.