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>

contracts-bedrock: cleanup tests

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>

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

contracts-bedrock: testing docs

contracts-bedrock: predeploys test

contracts-bedrock: migrate to new storage snapshot

Ensures that the predeploys are set and have the correct admin
slot set as well as have code present. It does not check what the
specific code is so that this can be ran against forked networks.

Now that we have the L2 contracts imported into the state via
`vm.loadAllocs`, we can begin to port the implementation of `check-l2`
into Solidity and reduce the amount of overhead a developer needs
to make changes to the contracts. The goal is to make as few changes
to other parts of the codebase when making changes to solidity files.

[check-l2](https://github.com/ethereum-optimism/optimism/blob/develop/op-chain-ops/cmd/check-l2/main.go)
runs against the devnet to ensure that the genesis state is correct. Now
we can make those assertions directly in solidity and deprecate the
concept of `check-l2`. We should be able to still run the solidity tests
against forked backends if we write the code in a modular way, so that
we can still run the tests against live networks or devnets.

contracts-bedrock: better setup check

Allows the specific game types to retain the contract wrapper with full type information instead of being limited to the generic interface.

Support creating different contract wrappers.

feat(ctb): Make `GENESIS_BLOCK_NUMBER` public

op-node: specify Delta upgrade version, update superchain-registry, bump protocol-support to Delta pre-release

Check the fs for the file before invoking the bash script as a sanity
check to save extra work when everything is running in parallel.

chore(ctb): Restructure `test` folder