fix(L1): leave time for schedule propagation

[jackchuma]

What changed? Why?

• Extend ProtocolVersions.FREEZE_WINDOW from 30 minutes to one hour, independently of MIN_NOTICE, so finalized readers have time to observe schedule changes before the sequencer-drift horizon makes the prior schedule reachable.
• Add regression coverage for the finalized-read buffer and retain the existing exact-boundary coverage.
• Refresh the ProtocolVersions semver lock because the contract bytecode changes.

Notes to reviewers

• The one-hour window covers the post-Fjord 30-minute maximum sequencer drift plus the default finalized reader's nominal 27m48s observation latency, leaving a 2m12s margin. This is a bounded contract-side mitigation; consumers must still reject stale schedule changes when finality or delivery delays exceed that assumption.

How has it been tested?

• just test --match-path test/L1/ProtocolVersions.t.sol (80 passed)
• just lint-check
• just test (1,221 passed, 1 skipped)

[cb-heimdall]

✅ Heimdall Review Status

Requirement	Status	More Info
Reviews	✅ 1/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1