Bump streamingfast/reth to base-v2.3.0-fh3.2

[sduchesneau]

Bumps the streamingfast/reth pin from base-v2.3.0-fh3.1 to base-v2.3.0-fh3.2 to pick up the finality fix in streamingfast/reth#29.

What the bump fixes

Every FIRE BLOCK line carried the node's finalized head as of the moment the block executed, with nothing requiring that block to be an ancestor of the one being emitted. Firehose transmits finality as a bare block number, so a block from a side branch was published with a LIB naming the canonical chain's block at that height — downstream marked it irreversible, then saw it replaced by the reorg.

It surfaced on BSC, where Parlia finality trails the head by two blocks and a four-block side branch was published with a LIB from the canonical chain — one of those blocks naming a height above its own number. On Base the finalized head normally sits far below any fork point, so the clamp returns it unchanged and nothing moves; it only bites when a reorg crosses the finalized height, and then the failure is identical.

Changes

• 71 streamingfast/reth pins bumped in Cargo.toml. The streamingfast/evm (v0.36.0-sf) and paradigmxyz/reth pins are untouched.
• Changelog entry in CHANGELOG.sf.md under ## Unreleased — rename or fold it into the release section as you see fit.

Blocked on

• The base-v2.3.0-fh3.2 tag being cut on streamingfast/reth (firehose: advertise finality only for ancestors reth#29 is merged into release/base-2.x). Until then this cannot resolve or build.
• Cargo.lock is untouched: its 130 ?tag=base-v2.3.0-fh3.1#<sha> entries need the tag's commit. A plain cargo build (or cargo update) refreshes them once the tag exists.