Merge pull request #8151 from ethereum-optimism/dependabot/npm_and_yarn/typescript-eslint/eslint-plugin-6.11.0

build(deps-dev): bump @typescript-eslint/eslint-plugin from 6.10.0 to 6.11.0

Version Packages

fix(sdk): bug in supportsTokenPair

Bumps [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) from 6.10.0 to 6.11.0.
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v6.11.0/packages/eslint-plugin)

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

op-chain-ops: add additional assertions the `check-l2`

Merge pull request #8153 from ethereum-optimism/dependabot/npm_and_yarn/typescript-eslint/parser-6.11.0

build(deps-dev): bump @typescript-eslint/parser from 6.9.1 to 6.11.0

build(deps): bump @sentry/node from 7.77.0 to 7.80.0

Bumps [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) from 6.9.1 to 6.11.0.
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v6.11.0/packages/parser)

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

build(deps-dev): bump tsx from 3.14.0 to 4.1.1

Merge pull request #8152 from ethereum-optimism/dependabot/npm_and_yarn/prettier-plugin-solidity-1.2.0

build(deps-dev): bump prettier-plugin-solidity from 1.0.0-beta.18 to 1.2.0

chain-mon: Use xlarge resource class when building chainmon docker.

Matches what it uses for releases.

op-challenger: Add a provider selector function for split output games

Fixes a bug in the supportsTokenPair where unsupported token interfaces
would cause the SDK to error out. Happens because the adapters check for
things that are only present in certain types of tokens. Adds a new
error handling check that wraps all sub-calls to supportsTokenPair in
each of the adapters so that the adapters don't need to worry about
this.

Bumps [prettier-plugin-solidity](https://github.com/prettier-solidity/prettier-plugin-solidity) from 1.0.0-beta.18 to 1.2.0.
- [Release notes](https://github.com/prettier-solidity/prettier-plugin-solidity/releases)
- [Commits](https://github.com/prettier-solidity/prettier-plugin-solidity/compare/v1.0.0-beta.18...v1.2.0)

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

Bumps [@sentry/node](https://github.com/getsentry/sentry-javascript) from 7.77.0 to 7.80.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.77.0...7.80.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 [tsx](https://github.com/privatenumber/tsx) from 3.14.0 to 4.1.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/v3.14.0...v4.1.1)

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

The `check-l2` script works against new networks but not legacy
networks. We need a solution that can work against both new networks
and legacy networks. This adds test coverage for new networks
as `check-l2` runs in CI against the local devnet.

Add test coverage for reinitialize on L2 contracts.
Also ensures that the `_initialized` value is set as
expected.

op-node,contracts-bedrock: setup `loadAllocs` usage

Modularize the `op-node` command for creating L2 genesis
blocks such that it can read a starting L1 block from disk
instead of needing to fetch it from a node. This makes the
process more simple and reproducible, because the block
JSON file can be written to disk and committed into a repo.

Also add the script for calling the `op-node` L2 genesis generation
to `contracts-bedrock`. It will create the L2 genesis state
in `contracts-bedrock/.testdata` which will be read by
`vm.readAllocs(string)` to populate the initial state.

Specify CI builder image

This should help fix the issue that CI can easily be broken if the CI image is not compatible and helps make it possible to test the CI image.

fix(indexer): bridge starting height marker

chore(ci): Bump foundry version

feat(ci-builder): Add `install-foundry` script to detect commit SHAs with `nightly` tags

contracts-bedrock: fix contracts flake in CI

Merge pull request #8079 from ethereum-optimism/dependabot/npm_and_yarn/types/chai-as-promised-7.1.8

build(deps-dev): bump @types/chai-as-promised from 7.1.5 to 7.1.8

op-chain-ops: check for protocol version config

Adds a `STRICT_DEPLOYMENT=false` env var to the CI
for the foundry tests. There is a race condition with it
reading files from disk. The deploy process needs to get config
from disk and when all of the foundry tests run in parallel,
sometimes particular tests will think the files do not
exist.

Ideally we can figure out a way to express to foundry "do something
only once" and then checkpoint the state, kind of like a meta `setUp`
but this doesn't seem to be possible, `setUp` is called many times.

improve naming consistency of Config struct variables