[Tracker] OPCM Upgrades

[maurelian]

High level description of project.

This is a tracking issue for the work outlined in the L1 Upgrades Design Doc.

L1 Contracts

• OZ V5 or custom unstructured Initializable implementation #13071
• Add an upgrade() function to all L1 contracts #13072
• Add all necessary contracts to the SystemConfig’s Addresses struct #13073
• New InitializedResetter contract #13074

OPCM changes

• New release() getter to represent the release #13076
• -rc is removed when upgrade() is called by the Upgrade Controller. #13077
• New upgrade() method #13078
• OPCM: New addGameType() method #13070

Testing

• Ensure tests run against both the fresh and upgraded system. #13079
• Testing to detect when a release has occurred and any non-empty upgrade() methods should be reset. #13080

OP Deployer changes

• op-deployer changes for OPCM upgrades #13081
• superchain-registry changes - Design and implement the mechanism for mapping release versions to an OPCM #13082

Label Checks

• I have added the team label for this project (CH, TH, Contributions).
• I have added the timeline for this project to the issue.