feat: add network-specific pre-state execution in decoder

[Nashtare]

• adds pre-execution rule specific to cdk-erigon
• fix precompile range
• couple tweaks in KERNEL constants module (state keys are hashes of addresses, not the addresses themselves, etc..)

What I haven't done:

• including the scalable / GER touched slots into prefetching for native tracer. Will we even care about using native tracer with CDK-erigon, or always rely on the Zero tracer? cc @muursh
• sanity checks based on target network in the decoder entrypoint. Should we assume the data being fed to be valid or do we want those? (i.e. no withdrawals for non-eth mainnet, no GER data for non-cdk-erigon, etc..) cc @0xaatif

closes #604

[atanmarko]

OK from the zero side.

[Nashtare]

@LindaGuiga let me know if you still need clarifications on the items above

@0xaatif would you want me to apply the last suggestion of #643 here or should we keep exploring options?

[0xaatif]

I think it's a great suggestion :) happy for it to be included