fix(ctb): remove unnecessary ERC20 factory code

fix(ctb): missing FeeVault comments

feat(ctb): remove unnecessary ERC721 factory code

feat(ctb): receivedMessages => failedMessages

Removes a legacy getter that was mistakenly added to the ERC20 factory.
We never had a getter for the bridge variable.

Adds missing constructor comments in the FeeVault contracts.

First removes the legacy bridge and remoteChainId getter functions.
Since the ERC721 factory is being deployed at a new address, it's not
necessary to maintain ABI compatibility. We can safely remove these
functions. Also removes constructor checks that aren't really necessary
since we can always upgrade if needed and the odds of getting something
like that wrong don't seem significant enough to warrant extra code.

fix(ctp): Downgrade `contracts-bedrock` dep to fix CI

Version Packages

Trigger release

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

fix(ctb): correct GPO abi and layout (#4582)

Fixes some small errors in the GPO's API and storage layout that did not
conform to the standards for how we are ugprading the L2 system.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Trigger Release

Changes the name of the receivedMessages variable to failedMessages.
Original name was confusing as it suggests that all messages will be
recorded in that mapping, even though only failed messages are recorded
in that mapping. Has created issues on several occasions.

op-node: Fix too eager advance in batch queue

op-node: Add stubbed Goerli config

op-chain-ops: better deploy config validation

feat(ctb): check for relayed legacy messages

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

op-chain-ops: make the migrated withdrawals version 0

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.