op-deployer: add 'inspect superchain-registry' subcommand

[bitwiseguy]

Closes #12612

Adds the following command to generate a .env file (written to /<working-dir>/superchain-registry.env:

./bin/op-deployer inspect superchain-registry <chain-id>

The .env output file can then be copied over to the superchain-registry and used for the just add-chain command.

Tests

I manually tested that the just add-chain command runs without failure up until the point where it tries to start making contract calls, which it cannot complete since the contracts in the test are only deployed to a local env

[mslipper]

A couple of notes on this:

• The intent file describes how you want your chain to look on L1. Only values required to actually deploy a chain should exist in the intent.
• The state file describes what steps op-deployer has taken for a given deployment, and their outputs. Similarly, only values required for a deployment should exist in state.
• Inspect commands read the state and intent files plus whatever additional context is needed from the user, then return some output.

Given the above, there's no need to modify the pipeline, state, or intent code to fulfill the requirements of this ticket. All you have to do is define an inspect command that read the state/intent, and takes some CLI flags to populate the other env vars.

[bitwiseguy]

there's no need to modify the pipeline, state, or intent code to fulfill the requirements of this ticket

I'm confused by this since there is this bullet item in the DoD for the ticket associated with this work. Can you help clarify?

Add fields to the intent relevant to the registry, e.g. SCR_CHAIN_NAME.

[mslipper]

lgtm