feat(op-deployer): Proxy bootstrap command

[clabby]

Overview

Adds a new bootstrap command to op-deployer that deploys an implementation-less 1967 Proxy. This is useful to have for one-off proxy deployments, such as when making a new FaultDisputeGame and replacing the DelayedWETH proxy it references.

[codecov]

Codecov Report

Attention: Patch coverage is 1.66667% with 118 lines in your changes missing coverage. Please review.

Project coverage is 42.26%. Comparing base (53b3af7) to head (ffc20a6).
Report is 3 commits behind head on develop.

Files with missing lines	Patch %	Lines
op-deployer/pkg/deployer/bootstrap/proxy.go	0.00%	116 Missing ⚠️
op-deployer/pkg/deployer/opcm/proxy.go	50.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #13213      +/-   ##
===========================================
- Coverage    46.95%   42.26%   -4.69%     
===========================================
  Files          923      756     -167     
  Lines        77648    68008    -9640     
  Branches       849        0     -849     
===========================================
- Hits         36456    28745    -7711     
+ Misses       38584    36885    -1699     
+ Partials      2608     2378     -230     

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/flags.go	0.00% <ø> (ø)
op-deployer/pkg/deployer/opcm/proxy.go	50.00% <50.00%> (ø)
op-deployer/pkg/deployer/bootstrap/proxy.go	0.00% <0.00%> (ø)

... and 176 files with indirect coverage changes

[ajsutton]

Will leave to slipper to review for correctness but it generally looks good to me. I wonder if it's worth having an option to specify the implementation to use. May not be a good idea since we often need to upgradeAndCall so we can initialise in one step but thought I'd mention it.

I can also see this would often be best as something that we utilise in other scripts that would initialise things rather than just deploying this then having to build a superchain-ops task to init it etc. I like the general idea of having small little scripts like this that can then be easily combined though.

[mslipper]

I fixed the code review items. LGTM now.