`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

Co-authored-by: Sebastian Stammler <seb@oplabs.co>

fix(ctb): snapshots exec

challenger: Begin supporting new OutputBisectionGame contract

contracts-bedrock: delete old storage layout

contracts-bedrock: delete state diff json

fix(ctb): readd type field to storageLayout snapshot

Removes the `deploy.json` state diff artifact. We don't necessarily
need to commit the state diff of the deploy script to the repo. We
should utilize the state diff of the deploy script when doing major
refactors of the deploy script to ensure that no bugs are being
introduced.

Adding in CI checks that the artifact has been updated is too much
overhead and not really worth the benefit. Certain changes to the deploy
script would result in huge diffs to the artifact without it being
particularly legible. This tooling is more useful for `superchain-ops`
where we should have every single storage slot diff fully accounted for.

The `.storage-layout` was replaced with a better equivalent with JSON.
The diffs in storage layouts should be easier to compare in the JSON
rather than in `.storage-layout` because of the way that the markdown
is rendered. See https://github.com/ethereum-optimism/optimism/pull/8332.

An unsolved problem is the type information is lost in the storage
layout lock now. That is something that we need to solve for in the
future.

fix(ctb): fix abi/storage snapshot script

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

Add a basic coderabbit config file