op-deployer: Holocene deployment support

[mslipper]

The artifacts for v1.8.0 were generated from the tag op-contracts-v180-artifacts-base, which points to the branch proposal/contracts/v1.8.0-opcm-backport. The backport branch consists of proposal/contracts/v1.8.0 with the non-proxied OPCM backported.

The OPCM was deployed using the opcm bootstrap command. The PDG blueprints were updated using a custom script which you can find at the op-contracts-v180-blueprints-script tag.

As part of this PR, I also added a bunch of tests to assert that the semver versions of deployed contracts are correct. I'll add similar tests for mainnet once the gov vote passes.

[codecov]

Codecov Report

Attention: Patch coverage is 64.28571% with 25 lines in your changes missing coverage. Please review.

Project coverage is 43.03%. Comparing base (92513ea) to head (6cf283d).
Report is 1 commits behind head on develop.

Files with missing lines	Patch %	Lines
op-deployer/pkg/deployer/standard/standard.go	65.71%	11 Missing and 1 partial ⚠️
op-deployer/pkg/deployer/artifacts/locator.go	63.15%	4 Missing and 3 partials ⚠️
op-deployer/pkg/deployer/apply.go	58.33%	3 Missing and 2 partials ⚠️
op-deployer/pkg/deployer/state/intent.go	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #13483      +/-   ##
===========================================
- Coverage    47.42%   43.03%   -4.39%     
===========================================
  Files          944      776     -168     
  Lines        78864    69380    -9484     
  Branches       803        0     -803     
===========================================
- Hits         37400    29858    -7542     
+ Misses       38698    36980    -1718     
+ Partials      2766     2542     -224     

Flag	Coverage Δ
cannon-go-tests-32	?
cannon-go-tests-64	?
contracts-bedrock-tests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
op-deployer/pkg/deployer/bootstrap/opcm.go	47.53% <100.00%> (ø)
op-deployer/pkg/deployer/pipeline/init.go	59.40% <100.00%> (ø)
op-deployer/pkg/deployer/state/intent.go	45.37% <0.00%> (ø)
op-deployer/pkg/deployer/apply.go	51.27% <58.33%> (+1.05%)	⬆️
op-deployer/pkg/deployer/artifacts/locator.go	74.64% <63.15%> (+1.57%)	⬆️
op-deployer/pkg/deployer/standard/standard.go	51.97% <65.71%> (-1.41%)	⬇️

... and 179 files with indirect coverage changes

[blmalone]

We have a branch proposal/op-contracts/v1.8.0-opcm-backport that has the following diff with proposal/op-contracts/v1.8.0: proposal/op-contracts/v1.8.0...proposal/op-contracts/v1.8.0-opcm-backport. Slipper has added a script that deploys blueprints for a specified contract (i.e. PDG, ASR).

The branch proposal/op-contracts/v1.8.0-opcm-backport is an extension of the tag op-contracts-v180-artifacts-base - diff here. The branch includes the DeployBlueprint.s.sol script.

Of course, we also have all the necessary changes in DeployImplementation.s.sol so that op-deployer can work with the artifact bundle that's made from this backport commit (and stored in GCP).

Additionally, we have the new DeployOPCM.s.sol. This is a more recent script that deploys OPCM on it's own from standard data. That is, this script takes as input already deployed blueprints, implementations etc (anything OPCM needs).

When we run op-deployer bootstrap opcm from this branch, it'll use the new ASR & PDG blueprints that Slipper manually deployed along with the existing blueprints for v180.

[mslipper]

Reviewed this live with @blmalone, and reproduced the artifacts hash locally on his machine.

[blmalone]

Confirmed that the artifacts hash: 361ebf1f520c20d932695b00babfff6923ce2530cd05b2776eb74e07038898a6 is created from the tag op-contracts-v180-artifacts-base.

Looked at the op-contracts-v180-artifacts-base diff with the v180 backport branch proposal/op-contracts/v1.8.0-opcm-backport. The changes introduced makes sense.