This includes an op-e2e action test which can be used as a regression test
against the invalid epoch advancement. I also had to fix several other tests.

This bug is caused by the batch queue advancing to the next epoch prior to
having the full sequence window for that epoch. This occurs when auto generating
batches. Once it has generated all of the batches for the current epoch, it
creates the first batch of the next epoch before it should.

Note: I had to remove the assumption that the epoch of the safe head is
the same as the epoch inside the batch queue. This is not true when generating
the last batch of an epoch. We can advance the batch queue, but we don't
generate a safehead with the new origin.

op-chain-ops: do not allow 0 scalar

bedrock: hardcode L2 genesis coinbase

The `DeployConfig` value for the `GasPriceOracleScalar` should
not be allowed to be set to 0. If it is set to 0, it would effectively
make the L1 portion of the fee nothing. This isn't useful since
eip1559 is enabled which required ether to be burnt with
execution, meaning that free transactions are not allowed
on the network.

If this value is set to 0, it is most likely a bug in the config
and we do not want to lose money by charging no L1 portion of the
fee.

Removes the config option for being able to set
the coinbase of the bedrock transition block.
It is now always set to the sequencer fee vault
predeploy. This is one less config option that needs
to be set correctly. The coinbase is always set to
the sequencer fee vault in bedrock blocks.

contracts-bedrock: deterministic storage

Makes the storage slot deterministic for the unsafe
block signer. This is useful because the `op-node` uses
a storage proof to fetch the value, so the `op-node` can
compute the storage slot value locally. This decouples
the way that `solc` lays out storage from the network policy,
making bugs less likely to happen when changing the contracts.

* bmon: Detect at warning and danger level balances

* bmon: Simplify by reducing to a single threshold

* bmon: Set amounts in eth rather than wei

* bmon: Add ops genie alert creation

* bmon: Add ops genie heartbeat

* bmon: Prep for goerli

op-e2e: action-test extended time without batches in L1 blocks

op-e2e: action test derivation with flaky L1 RPC

op-node: allow sequencer to produce block with txs at sequencer time drift boundary

bmon: Add basic alerting logic

op-node: allow sequencer to produce block with txs at sequencer time drift boundary to match derivation behavior

feat(ctb): deploy drippie to Goerli

Breaks out the SystemDictator steps into two files so that the steps
that get executed before the system is shut down can easily be separated
from the steps that executed after the system gets spun back up. Idea
here is that you would execute with the tag "steps1", wait for the
legacy system to come down, migrate the L2, then execute with the tags
"steps2" to complete the upgrade.

* op-node,op-e2e: optimize receipts fetching by supporting different kinds of rpc providers and receipts-fetching method alternatives

* op-node: rpc provider kinds / fetching methods review fixes

* op-e2e: add missing arg - fix lint

* op-chain-ops: Fix state migration, add post-checks

This PR fixes a bug in `op-chain-ops` that could cause state to become erroneously erased during the L2 migration. While testing the Goerli migration in check mode, I encountered an issue where `db.GetState` was returning null storage slots for the legacy message passer during the withdrawals portion of the migration. Upon further inspection, I discovered that we were using `db.CreateAccount` in the `setProxies` method. `db.CreateAccount` will erase the state associated with the passed-in address, so I updated `setProxies` to check if the account exists first. I also added a map of predeploys that should _not_ be touched as part of the migration process at all. At the end of the migration process, I iterate over these "untouchable" contracts and make sure that their code matches a preset list of code hashes and sample up to 5,000 storage slots before and after the migration to make sure the match.

Additionally, I found a bug in the witness generation data within `l2geth`. The witness generation code for the message passer does not take reverts into account. There's no easy way to do this, since we don't have access to the call frame in which the revert occurred. To work around this, I added the ability to ignore reverted storage slots in the `ParamsByChainId` structure.

Lastly, I made a few miscellaneous changes to improve our confidence in the migration script:

- I added checks to the OVM ETH migration to ensure that state slots are properly preserved.
- I added a read cache to the underlying state DB so that repeated read calls are faster.

I have verified that this migration script works end-to-end with check mode enabled against a forked Goerli L1.

* Add hash checking in addition to sampling