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

rabbit: Try to reduce the amount of rabbit vomit on every PR

fix(ctb): Package pre-pr Target Fixes

Bumps [jsdom](https://github.com/jsdom/jsdom) from 23.0.0 to 23.0.1.
- [Release notes](https://github.com/jsdom/jsdom/releases)
- [Changelog](https://github.com/jsdom/jsdom/blob/main/Changelog.md)
- [Commits](https://github.com/jsdom/jsdom/compare/23.0.0...23.0.1)

---
updated-dependencies:
- dependency-name: jsdom
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

build(deps): bump viem from 1.19.9 to 1.19.11

build(deps-dev): bump tsx from 4.6.0 to 4.6.1

feat(ctb): Cannon Output Bisection Game Implementation

Bumps [@sentry/node](https://github.com/getsentry/sentry-javascript) from 7.82.0 to 7.84.0.
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/getsentry/sentry-javascript/compare/7.82.0...7.84.0)

---
updated-dependencies:
- dependency-name: "@sentry/node"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [@swc/core](https://github.com/swc-project/swc) from 1.3.99 to 1.3.100.
- [Release notes](https://github.com/swc-project/swc/releases)
- [Changelog](https://github.com/swc-project/swc/blob/main/CHANGELOG.md)
- [Commits](https://github.com/swc-project/swc/compare/v1.3.99...v1.3.100)

---
updated-dependencies:
- dependency-name: "@swc/core"
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [viem](https://github.com/wevm/viem) from 1.19.9 to 1.19.11.
- [Release notes](https://github.com/wevm/viem/releases)
- [Commits](https://github.com/wevm/viem/compare/viem@1.19.9...viem@1.19.11)

---
updated-dependencies:
- dependency-name: viem
  dependency-type: direct:production
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [tsx](https://github.com/privatenumber/tsx) from 4.6.0 to 4.6.1.
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/develop/release.config.cjs)
- [Commits](https://github.com/privatenumber/tsx/compare/v4.6.0...v4.6.1)

---
updated-dependencies:
- dependency-name: tsx
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

contracts-bedrock: cleanup tests

Disables high level summaries and review status so hopefully we just get the actual suggested changes.

fix(ctb): Concrete game types

fix(ctb): Concrete game types

Use the `vm.expectEmit(address)` over the variant that uses all of the
booleans when they are all true. This reduces code and makes it easier
to read for reviewers. Each boolean means if the log topic/data should
be compared. Generally, we want them to all be true which is why the
short hand of just expecting it to come from an address exists, that
assumes all of the values are true and asserts it emits from the
address. We should always follow this style of `vm.expectEmit` unless
there is a good reason not to, ie its not known that a particular topic
will be or it is too complex to compute it. If this is the case then
perhaps the smart contract is too complex and the architecture needs to
be thought about more.

op-node: Add syncmode flag and remove old snap sync flag