Make reth data pipeline privacy aware

[phexyz]

Overall changes:

the value type was U256 before but it is FlaggedStorage, per changes from seismic-revm SeismicSystems/seismic-revm#9. Revm inspectors needed to run this
SeismicSystems/seismic-revm-inspectors#1

Testing:

run make test. 2 lock-file-test will fail per paradigmxyz/reth#9381

Modified seismic-reth/crates/storage/provider/src/writer/mod.rs:731 to check if is_private flag is committed to database from evm execution outcome
Modified seismic-reth/crates/trie/trie/src/state.rs:347 to check if is_private flag is propagated from hashedStorages to postHashedStorages

Diff doc:

1. State root calculation: we don’t encode the is_private flag during the state_root calculation ([code](5a69f1e#diff-a69280a7601140010b48c98e07c58431efd9e6f45180dcfcd2e0d423e4588a98R162)). However, we might want to include is_private as part of the state since a storage slot can transition from public to private
2. RPC: if is_private is true, we return 0 when called eth_storageAt ([code](f26de3b)) The reason is that given your storage can go from private to public, you might be leaking information by just enumerating the storage type. Second issue is that returning zero might be misleading if there is really any value being stored. For complete set of code paths where this choice affected, please to for all places where encode_fixed_size() is called. All other rpc calls are not impacted by this PR
3. we put is_private flag along with addr_key as the key instead of combining with the value during parallelization of StorageHashingStage seismic-reth/crates/stages/stages/src/stages/hashing_storage.rs:106

[sfyll]

100 push ups