Since we're checking every slot in the legacy message passer, we need to pass in the full list of messages to the message passer for verification purposes then filter out messages from senders other than the L2XDM prior to executing the withdrawals migration. This PR fixes the filtering, and adds a check in the withdrawals post-check step to make sure that no potentially fraudulent withdrawals get migrated.

Fixes CLI-3379

maint(ctb): revamp the rekey task

proxyd: Remove logging

Version Packages

Develop -> Master

op-node: Fix `Frame` parsing

proxyd: Add global flag to method overrides

This allows us to set global limits on individual RPCs that ignore any origin/user agent exemption.

txmgr: Don't submit underpriced replacements

Don't log warnings when legacy block gossip validation fails

fix(op-node): Require chain IDs to be positive

feat(ctb): add getting-started network

Update op-geth

Adds the getting-started network and configuration for the OP Stack
Getting Started guide.

op-chain-ops: more strict checks for config validity

Update the update-op-geth script to account for removal of go.work

feat(opn): expose GasUsed in BlockInfo type

fix(ctb): Add creation time check for `SUBMISSION_INTERVAL` > `L2_BLOCK_TIME`

Exposes the GasUsed field in the BlockInfo type. This has no impact on
the op-node for Optimism Mainnet, but it will be used in the OP Stack
Getting Started guide.

Improve error wording

Adds in additional sanity checks for the config validity
to prevent accidental bad configurations of the L2 predeploys.
Ensures that specific values are set in the immutables. Note
this this makes the immutables config specific to optimism,
previously it was implemented in a generic way using a map
so that it could be used with other projects that are doing
similar things with setting contracts in state with their immutables
preset. We could turn it into a struct instead of using a map
which could make it easier to use.

Tests were updated as the data in the tests failed the validation.

This handles the case that a transaction is being resubmitted while
the L1 Basefee & Tip have not increased. In this case we reuse the
previous values. If the new values are between the old values & the
threshold, we then increase that value to the threshold. If it is
larger than the threshold, we then use the suggested value.

We need to not always bump the transaction price to ensure that we
don't go exponential when resubmitting transactions.

fix(op-node): Increase gossip seenMessagesTTL