Bump reth to base-v2.5.2.3-fh3.1-1

[sduchesneau]

Points streamingfast/reth at base-v2.5.2.3-fh3.1-1 (streamingfast/reth#40, merge commit a44598533b) and opens the v1.3.2-fh3.1-1 changelog section.

The only change it brings is the 256-byte cap on keccak preimages. Values in Call.keccak_preimages could reach 65536 bytes each (131072 hex characters). The map is there so a consumer can walk a storage slot back to the expression that produced it, and Solidity's slot derivations are small: 32 bytes for a dynamic array or a bytes/string longer than 31 bytes, 64 bytes for a mapping with a value-type key, and 32 bytes plus the key for a mapping(string => V). 256 bytes covers all of those with 224 bytes of room for a dynamic key. Oversized preimages are dropped rather than truncated, since a truncated preimage no longer hashes back to its map key.

No source change is needed here — the cap lives in the reth fork's crates/firehose/src/inspector.rs. The replay fixture block.49663794.json holds one 64-byte preimage, under the cap, so it does not need regenerating.

The tag base-v2.5.2.3-fh3.1-1 does not exist yet. Cargo.toml and Cargo.lock were updated by hand: the tag string and the locked rev (eb0f60e8e7 → a44598533b) were substituted across all 70 Cargo.toml and 106 Cargo.lock entries. The reth commit touches no Cargo.toml, so the dependency graph is unchanged and nothing else in the lock moves. CI will confirm once the tag is pushed.