* op-node,op-e2e: update libp2p libs, fix libp2p gossip settings

* op-node: docker.go.work formatting fix

* op-node: docker.go.work add missing service module

* op-node: build workaround, reference modules to try and fix docker build

feat(ctb): remove DeployConfig

Removes the DeployConfig contract. It seems this contract might've been
reintroduced as part of a merge conflict. We don't need this contract
anymore because all of the relevant structs are contained within the
BaseSystemDictator contract.

op-node: set initial system config gaslimit, check initial values

testmig: Remove in favor of op-e2e

feat(ctb): SystemConfig comments

ci: Fix devnet

Co-authored-by: protolambda <proto@protolambda.com>

Co-authored-by: protolambda <proto@protolambda.com>

Adds comments to SystemConfig functions and variables.

op-node: catch up L2 sequencing based on time, not L1 origins

* bedrock: update op-geth dependency

* chore: add changeset
Co-authored-by: Mark Tyneway <mark.tyneway@gmail.com>

* op-batcher: Rewrite ChannelManager

The channel manager is now responsible for tracking in flight frames
and properly handling different error conditions.

* op-batcher: String() & TerminalString() for txID

* op-batcher: Remove channelPending bool

* op-batcher: Fix wraparound bug in timeout check

* op-batcher: Comments + Logging

* op-batcher: Properly exit loop

* op-node: Prefer following seq drift instead of conf depth

We found a log on a testnet where a batch was rejected because it's
timestamp was greater than the origin timestamp + sequencer drift.
I looked into origin selection and determined we produce empty blocks
if the block time is ahead of the origin + seq drift; however if there
is a next origin, it is not enough to produce an empty block, we must
change the origin.

I hypothesize that this occurred because the L1 head that the node was
looking at was lagging. That would cause the node to keep using an
old origin even if the timestamp was past the max drift. I added
a unit test which shows this case & would fail without this fix
being applied.

* op-node: Don't immediately attempt to advance origin

If the current origin is past the sequencer drift, it needs to
ignore the conf depth staying, but does still need to check next
L2 block time against the next origin time.

I've also added a test for this case.

[op-node] Check that BlockNumber is non-nil in the receipt validation

deps: replace deprecated package with updated package

op-chain-ops: wrap errors

contracts-periphery: make the network name match contracts

ci: fix hardhat-node release

Bumped compiler version for contracts-bedrock

There was a typo in the config for building/publishing
the `ethereumoptimism/hardhat-node` docker image.
This fixes that typo so that builds can be properly
published to dockerhub.

https://github.com/miguelmota/go-ethereum-hdwallet is no longer
maintained and is using older versions of dependencies. There are
dependencies clashing when trying to update code elsewhere in the
codebase.

https://github.com/tynes/go-ethereum-hdwallet is a fork with updated
deps such that we can more easily update other deps in the codebase
and drop old deps.

This will make debugging the migration much easier by wrapping
errors during the migration.

* op-node,contracts-bedrock: dynamic gas limit via SystemConfig

* specs: fix gas limit type

* specs: test missing gas limit

* op-chain-ops: fix system config initialize call, use default L2 gas limit

* go: update op-geth dependencies for dynamic gas limit change

* op-chain-ops: fix 2nd missing default

This is required for tooling to work with the migration,
it expects that network names are consistent across packages.

Version Packages