For both the denominator and elasticity. They cannot be 0.

op-chain-ops: base fee check

op-chain-ops: safety with params

Check that the L2 genesis block base fee per gas
is not set to `nil`. If it is, it will cause a segfault
in `op-geth` on startup after the migration.

It is configured with the key: `"l2GenesisBlockBaseFeePerGas"`

Check for `nil` when getting the chain params.
Also log info about the chain params

Without it, there will be a `nil` dereference.
Each network should be added explicitly

op-migrate: use correct ancient path

op-chain-ops: better error handling in op-migrate

Remove changesets dir from codeowners

Prevent `nil` dereference by explicitly checking for `nil`.
Add in logs to give better understanding of what the script is
doing.

Merge pull request #4126 from ethereum-optimism/11-30-op-chain-ops_Migration_should_not_use_readonly

op-chain-ops: Migration should not use readonly

maint(ctb): clean up deploy config

op-chain-ops: more cleanup in migrate script

The `op-migrate` script had some leftover stuff
in it from early iterations on its development.
The leftover stuff was cleaned up to improve the
overall UX of the script. Now code should not need
to be commented out + rebuild the binary, it will
automatically detect when the script has already
ran on a datadir.

Also pass through the no check arg so that we can
re-enable the checking and dynamically change if
we want to run the data validation as part of the
migration.

op-chain-ops: set initial message passer nonce

The `L2ToL1MessagePasser` nonce is set to `type(uint32).max`
initially to prevent nonce collisions with legacy withdrawals
that have been upgraded. The max value for the nonce is
`type(uint256).max` so it is not a problem to start at a non
zero nonce.

op-chain-ops: no longer embed receipts

The functionality was added to create a bunch of receipts
as part of the bedrock transition so make the sdk and
withdrawal workflows "just work". We are going to instead
implement logic into the sdk instead of having the extra
receipts. The extra receipts would throw off data people.
It would look like withdrawals happened twice.

feat: op-migrate docker image

Was missing a `requires` statement

Adds a `migrate` binary as well as a dockerfile for
building it. This `Dockerfile` should be accessed from
the root of the repository, similar to the other docker
files for the other bedrock packages.

Cleans up the deployment configuration structs for contracts-bedrock.

docs: fix l2-output link

docs: fix typo `qn` -> `an`

op-chain-ops: various cleanup

Fixes a bug were an error should have been returned and it was not.
Wraps some errors so that its easier to tell what the problem is
in the case of there being an error. A bit of refactoring that
allows the strict withdrawal migration checks to be skipped optionally.
This should not be used in production, but can be used in early test
iterations.

op-chain-ops: add bedrock transition receipts

Cleanup code, refactor some interfaces, make logIndex canonical

To make withdrawals really easy, we need to add in
receipts corresponding to the migrated withdrawals.
This will allow the exact same flow to be used when
creating the withdrawing transactions as normal
withdrawals.

fix(ctb): break out clamp func in Metering