Only impacts deposits

Enable extended pause functionality in the standard bridge.
Includes updates to tests and the deploy script.

feat(ctb): Refactor `SemverLock`

contracts-bedrock: cross domain messenger comment

Improve the comment to make it more accurate in the `L1CrossDomainMessenger`.

docs: Fix broken PR guideline hyperlink

op-node: Remove Panic while Span Batch Derivation

op-chain-ops: cleanup immutables

op-e2e: Improve e2e test for span batches

Co-authored-by: clabby <ben@clab.by>

We really only need to know if a contract has immutables and not what
the immmutables are to write good tests to ensure that all contracts
that have immutables are covered in the L2 genesis generation. Adding in
the actual immutables references as a string resulted in a lot of diffs
because the ast ids where used in them. This updates the bindings to use
a boolean instead of the string. Now we can still tell if a contract has
immutables and we dont care about what the offsets are. This will not
result in a large diff for the smart contracts when ast ids change.
It will only flip a bool when immutables are added or removed from a
contract.

feat(op-challenger): alphabet output bisection game

contracts-bedrock: include `initialize` checks for L2 contracts

To also run the checks for L2 contracts with `initialize`, some
changes to the pipelie are required. First off, when foundry
compiles a single contract with 2 different versions of solc, it
appends the solc version to the name of the file. This broke some of the
tooling that we have around reading artifacts from disk. This commit
updates the tooling to first check to see if the file exists and if
not, then it grabs one of the multiple artifacts instead. This means
that we need to be careful about the artifact because it may not exactly
match what was used. There isn't a great way around this because its not
possible to know the compiler version used within the evm.

Also make some modifications that allow for the L2 predeploys to have
their contract addresses fetched based on name. The method isn't super
nice because it will require the script to be updated if new predeploys
are added but its not the end of the world because the tooling
likely will not be used with many different predeploys, and if it
is in the future we can solve the problem then. In go we handle this
problem with an `init` function that registers all of the predeploys
into a map that we can iterate over. That just isn't possible in
solidity.

Add test coverage over the `L2CrossDomainMessenger` to ensure that
it cannot be initialized. This is test coverage that unblocks the
following PRs:
- https://github.com/ethereum-optimism/optimism/pull/8353
- https://github.com/ethereum-optimism/optimism/pull/8365
Both of these are adding new L2 contracts that will be initializable and
we want this test coverage ahead of time to prevent reinit bugs from
being introduced.

op-bindings: fix develop breaking

fix(ctb): bad rebase

fix(op-challenger): split and game depth loading

chore(op-challenger): issue comments

revert output cannon trace type to 0

`develop` needs a regen of bindings because they got out of date

build(deps-dev): bump jsdom from 23.0.0 to 23.0.1

build(deps): bump @sentry/node from 7.82.0 to 7.84.0

op-chain-ops: strict immutable reference checking

monorepo: make devnet-up just works

build(deps-dev): bump @swc/core from 1.3.99 to 1.3.100

Ensure that the submodules exist as part of the
`make devnet-up` command. This enables somebody
to clone the repo and run a single command to bring
up the entire devnet without needing to worry about
running any other commands. Also replace some calls
in the CI to use `make` instead of `git` directly
for when installing the submodules.

chore(op-node): log transaction hash in warning