feat(L1): bind aggregate proofs to ProtocolVersions schedule

[PelleKrab]

Summary

Builds on #353.

Pins each AggregateVerifier game to the ProtocolVersions.scheduleId() that is active when the game
is initialized, and includes that pinned value in the TEE and ZK proof journals.

• scheduleId snapshot: games read PROTOCOL_VERSIONS.scheduleId() once during initialization and
  store it as scheduleId
• proof binding: TEE and ZK journal hashes now commit to the pinned schedule ID, so proofs are
  bound to the upgrade schedule that existed when the game was created
• deployment wiring: standard and dev multiproof deployment flows now pass the ProtocolVersions
  proxy into AggregateVerifier
• interface/tests: IAggregateVerifier exposes PROTOCOL_VERSIONS and scheduleId; tests cover
  that later schedule changes do not alter an initialized game's pinned value

Test plan

• forge test --match-path test/L1/proofs/AggregateVerifier.t.sol
• forge test --match-path test/L1/proofs/DisputeGameFactory.t.sol
• forge test --match-path test/L1/OptimismPortal2.t.sol
• forge test --match-path 'test/L1/proofs/*.t.sol'
• forge fmt --check

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/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 1 Sum 2