fix(lib): thread proposal_id and chain_id into ShastaData for anchor skip

[ggonzalez94]

Summary

• Add proposal_id field to RethBlockBuilder and thread batch_id through to ShastaData
• Add chain_id from ChainSpec to ShastaData
• These fields enable taiko-reth to conditionally skip the anchor success check for early mainnet Shasta proposals (1-7) where anchorV4() reverted during bootstrapping

Context

The first Shasta proposals on mainnet had reverted anchor transactions due to bootstrapping issues. The prover cannot generate valid proofs for these proposals because the consensus rule "anchor tx must succeed" fails. This change passes the proposal ID and chain ID through to the execution layer so it can make a targeted exception for those specific proposals.

Companion PRs

• taiko-reth: taikoxyz/taiko-reth#73 — the execution-layer change that conditionally skips the anchor check
• taiko-mono: taikoxyz/taiko-mono#21529 — client-side driver fix for reading anchor state during bootstrapping

Note

Once taiko-reth#73 is merged, this PR's Cargo.toml should be updated to point reth-* dependencies to the merged branch (or v1.0.0-rc.2-taiko-shasta if it's merged there).

Test plan

• Verify raiko compiles with updated taiko-reth dependency
• Generate proof for mainnet proposal 1-7 and verify success
• Generate proof for proposal >= 8 and verify anchor check still enforced
• End-to-end proof submission to Inbox.prove()

🤖 Generated with Claude Code