feat: small updates for steps tracing

[klkvr]

• Adds record_returndata_snapshots flag to config which enables snapshots of interpreter.return_data_buffer
• Adds record_opcodes_filter parameter which allows to only record specific opcodes. ref feat: identify internal function invocations in traces foundry-rs/foundry#8222 (comment)
• Adds gas_used field for CallTraceStep

This should be enough to migrate foundry's debugger to using TracingInspector from here, I will open PR for this later today.

[klkvr]

This PR conflicts with approved #84 as it relies on previous recorded step always containing memory during previous instruction. This wouldn't be true if record_opcodes_filter is configured

[DaniPopes]

We could just override the filter to say that we're tracing memory opcodes if we also want memory in that case

[mattsse]

We could just override the filter to say that we're tracing memory opcodes if we also want memory in that case

that makes sense

[klkvr]

We could just override the filter to say that we're tracing memory opcodes if we also want memory in that case

hmm, perhaps we should just fallback to old behavior in that case? if user provided filter to only collect JUMPs for example it might be unexpected that we'd collect 11 other opcodes as well potentially increasing memory usage

[mattsse]

if I'm reading this correctly, then this does not change the existing recording logic and only adds returndata recording based on opcode filter?

the overhead is negligible here

we can do @DaniPopes suggestion separately I believe

[mattsse]

I do remember we had this at some point

[mattsse]

lgtm, pending @DaniPopes

[klkvr]

if I'm reading this correctly, then this does not change the existing recording logic and only adds returndata recording based on opcode filter?

opcode filter and returndata are separate configs

returndata is recorded in the same way as memory: if record_returndata_snapshots is true, we always save snapshot

and opcode filter is just a way to make tracer record only specific steps to optimize memory usage if we're only interested in a small subset of steps. e.g. this is the case for internal fns tracking in foundry where we only want JUMPs and JUMPDESTs along with their stack and memory snapshots