op-deployer: add intent-config-type

[bitwiseguy]

Creates the concept of intent-config-type. Based on the selection, some fields are auto-populated and others are expected to be populated by the user prior to running op-deployer apply. Valid options are:

• test used by current test suite, deterministically generates addresses/keys used in testing
• standard (default, uses standard values as defined in superchain-registry where possible)
• custom requires all params to be populated by user, errors during apply if any don't get set
• strict same as "standard", but sets additional params
• standard-overrides
• strict-overrides

Design Details

• op-deployer init
  • intent.SetInitValues: generates initial intent (with many empty fields)
  • user expected to fill out empty/zero-value fields before running op-deployer apply
• op-deployer apply
  • pipeline stage: init
    • intent.ValidateIntentConfigType: validates that all fields have been populated, and that values meet expectation (e.g. standard values are used if intent-config-type=standard

Open questions

Which fields should thestandard-overrides/strict-overrides settings allow to be overridden? The way this is currently implemented:

• standard-overrides:
  • op-deployer init: sets intent.toml standard values
  • op-deployer apply: validates that all values are populated (i.e. non zero value) but doesn't require specific values
• strict-overrides:
  • op-deployer init: sets intent.toml strict values
  • op-deployer apply: validates that all values are populated (i.e. non zero value) but doesn't require specific values

Meta

Closes https://github.com/ethereum-optimism/platforms-team/issues/305

[mslipper]

A few issues I'd like to address before merge. Happy to pair next week to resolve them.

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 124 lines in your changes missing coverage. Please review.

Project coverage is 42.81%. Comparing base (9109958) to head (55376b2).
Report is 1 commits behind head on develop.

Files with missing lines	Patch %	Lines
op-deployer/pkg/deployer/state/intent.go	49.15%	80 Missing and 10 partials ⚠️
op-deployer/pkg/deployer/standard/standard.go	32.00%	17 Missing ⚠️
op-deployer/pkg/deployer/init.go	0.00%	6 Missing ⚠️
op-deployer/pkg/deployer/state/chain_intent.go	82.35%	4 Missing and 2 partials ⚠️
op-deployer/pkg/deployer/apply.go	0.00%	2 Missing and 1 partial ⚠️
op-deployer/pkg/deployer/pipeline/init.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #12970      +/-   ##
===========================================
- Coverage    44.46%   42.81%   -1.66%     
===========================================
  Files          798      743      -55     
  Lines        71682    67175    -4507     
===========================================
- Hits         31876    28762    -3114     
+ Misses       37219    35990    -1229     
+ Partials      2587     2423     -164     

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

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

Files with missing lines	Coverage Δ
op-deployer/pkg/deployer/artifacts/locator.go	82.60% <100.00%> (+0.97%)	⬆️
op-deployer/pkg/deployer/flags.go	62.50% <ø> (ø)
op-deployer/pkg/deployer/pipeline/init.go	32.74% <0.00%> (ø)
op-deployer/pkg/deployer/apply.go	49.33% <0.00%> (-0.67%)	⬇️
op-deployer/pkg/deployer/init.go	0.00% <0.00%> (ø)
op-deployer/pkg/deployer/state/chain_intent.go	82.35% <82.35%> (ø)
op-deployer/pkg/deployer/standard/standard.go	49.59% <32.00%> (+0.09%)	⬆️
op-deployer/pkg/deployer/state/intent.go	46.69% <49.15%> (+46.69%)	⬆️

... and 66 files with indirect coverage changes