Summary

#3246
This PR completes the map-foldhash feature propagation across the revm workspace, enabling users to leverage the faster foldhash algorithm for HashMap operations throughout the entire dependency chain, including the revme binary and statetest-types crate.

Problem

The map-foldhash feature enables the foldhash algorithm (via alloy-primitives/map-foldhash) for improved HashMap performance. Previously, this feature was only partially implemented:

• Defined in: revm-primitives and revm crates
• Missing from: revm-state, revm-database, revm-context, statetest-types, and revme

This incomplete propagation caused the following issues:

1. Users couldn't enable map-foldhash when building revme:

   cargo build -p revme --features map-foldhash
   # error: the package 'revme' does not contain this feature: map-foldhash

2. The feature didn't propagate through the statetest-types dependency chain, limiting its effectiveness when running Ethereum state tests.

3. Intermediate crates (state, database, context) couldn't forward the feature to their dependencies, breaking the feature propagation chain.

Broken Feature Chain (Before)

revme
  └─> revm (with test-types)
        └─> statetest-types ❌ (no map-foldhash feature)
              ├─> primitives ✓
              ├─> state ❌ (no map-foldhash feature)
              ├─> context ❌ (no map-foldhash feature)
              └─> database ❌ (no map-foldhash feature)

Solution

Added map-foldhash feature definitions to all crates in the dependency chain.

Validation Commands

All of the following commands should succeed after this change:

# Individual crate checks
cargo check -p revm-state --features map-foldhash
cargo check -p revm-database --features map-foldhash
cargo check -p revm-context --features map-foldhash
cargo check -p revm-statetest-types --features map-foldhash

# Main crate with combined features
cargo check -p revm --features "std,map-foldhash,test-types"

# Revme binary (end-to-end validation)
cargo build -p revme --features map-foldhash

# Workspace-wide check
cargo check --workspace --features map-foldhash

Notes

• The implementation follows revm's existing feature flag patterns
• Uses optional dependency syntax (statetest-types?/map-foldhash) to handle conditional dependencies correctly (crates/revm/Cargo.toml)
• Maintains no_std compatibility (feature only affects HashMap implementation, not allocator requirements)
• No breaking changes; this is purely an enhancement to feature flag propagation