fix: record selfdstructs properly

[mattsse]

closes #3919

selfdestructs are no separate call so the way we convert to parity action is likely wrong because this swallows the call action

Selfdestructs need to be derived from the call that triggered and are additional trace objects

this adds an iterator type that can handle this

[codecov]

Codecov Report

Merging #3921 (92dd7b9) into main (73652ed) will decrease coverage by 0.06%.
Report is 7 commits behind head on main.
The diff coverage is 0.00%.

Files Changed	Coverage Δ
...revm/revm-inspectors/src/tracing/builder/parity.rs	0.00% <0.00%> (ø)
crates/revm/revm-inspectors/src/tracing/types.rs	0.00% <0.00%> (ø)

... and 11 files with indirect coverage changes

Flag	Coverage Δ
integration-tests	16.32% <0.00%> (-0.02%)	⬇️
unit-tests	64.27% <0.00%> (-0.05%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
reth binary	26.67% <ø> (ø)
blockchain tree	83.04% <ø> (ø)
pipeline	89.82% <ø> (ø)
storage (db)	74.30% <ø> (ø)
trie	94.70% <ø> (ø)
txpool	45.40% <ø> (ø)
networking	77.63% <ø> (-0.04%)	⬇️
rpc	58.52% <ø> (+0.01%)	⬆️
consensus	63.51% <ø> (ø)
revm	32.71% <0.00%> (-0.38%)	⬇️
payload builder	6.58% <ø> (ø)
primitives	87.92% <ø> (-0.02%)	⬇️

[onbjerg]

Is #3863 related to #3919?

[mattsse]

could be the same issue

I'd actually say likely because this affects all selfdestruct calls

[rkrasiuk]

lgtm