fix: exclude calls to precompiles in parity tracers

[mattsse]

ref #2970

This adds a is_precompile marker to the tracer types and excludes nodes that are precompiles

@rakita how do I find out if a call is to a precompile?

UPDATE

This currently patches https://github.com/bluealloy/revm/tree/release/v25
@rakita what#s the ETA for revm release that includes this?

[codecov]

Codecov Report

Merging #2987 (db86e7b) into main (2e11c6f) will decrease coverage by 0.02%.
The diff coverage is 3.22%.

@@            Coverage Diff             @@
##             main    #2987      +/-   ##
==========================================
- Coverage   70.86%   70.84%   -0.02%     
==========================================
  Files         520      520              
  Lines       68260    68294      +34     
==========================================
+ Hits        48372    48383      +11     
- Misses      19888    19911      +23     

Flag	Coverage Δ
integration-tests	17.04% <3.22%> (+<0.01%)	⬆️
unit-tests	65.80% <0.00%> (-0.02%)	⬇️

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

Impacted Files	Coverage Δ
...revm/revm-inspectors/src/tracing/builder/parity.rs	0.00% <0.00%> (ø)
crates/revm/revm-inspectors/src/tracing/mod.rs	0.00% <0.00%> (ø)
crates/revm/revm-inspectors/src/tracing/types.rs	0.00% <0.00%> (ø)
crates/revm/revm-inspectors/src/tracing/config.rs	30.35% <14.28%> (-2.30%)	⬇️

... and 8 files with indirect coverage changes

[rakita]

ref #2970

This adds a is_precompile marker to the tracer types and excludes nodes that are precompiles

@rakita how do I find out if a call is to a precompile?

Currently, you can't, but we can move procompiles to EVMData. PR here: bluealloy/revm#504