perf(storage): add bloom filter for empty storage slots

[gakonst]

Summary

Implements a bloom filter to short-circuit storage reads for empty slots, potentially avoiding RocksDB lookups for 30-40% of storage reads.

Based on analysis from Nethermind's FlatDB work (PR #9854):

• Mainnet has ~500M-1B non-empty storage slots
• A bloom filter can definitively say 'not present' for empty slots
• Potential 10-20% mgas/s improvement on some block ranges

Architecture

• New reth-storage-bloom crate with GrowableBloom filter
• BloomStateProvider wrapper that checks bloom before DB access
• Metrics for bloom hits, misses, and false positives
• Persistence support for saving/loading bloom to disk

Trade-offs

From Nethermind's experience:

• Memory: ~1-2GB for mainnet scale at 1% false positive rate
• Write amplification: Every storage write updates bloom
• Uncertain ROI: Depends heavily on workload characteristics

How to Test

This is feature-gated behind storage-bloom flag. To enable:

reth-provider = { features = ["storage-bloom"] }

Benchmark Request

Need to benchmark on mainnet block re-execution to measure:

1. Storage read reduction (bloom hit rate)
2. False positive rate
3. Overall mgas/s impact
4. Memory overhead

cc @brian @alexey - please review benchmark results when available

Closes

Closes #21184

[gakonst]

Benchmark Started 🚀

The CodSpeed benchmark workflow is running: https://github.com/paradigmxyz/reth/actions/runs/21133685427

Note: This is the standard bench workflow. For proper mainnet block re-execution benchmarks to measure the bloom filter impact, we'll need to run manual benchmarks on a reth box.

What to measure:

1. Storage read reduction - bloom hit rate (how many reads avoided DB)
2. False positive rate - bloom said 'maybe present' but DB returned empty
3. Overall mgas/s impact - with vs without bloom
4. Memory overhead - actual bloom filter size at scale

cc @brian @alexey - will need to coordinate a manual benchmark run on reth3/reth5 to get meaningful numbers.

[mediocregopher]

Integrate into the payload validator in engine tree