build(deps-dev): bump vitest from 0.34.1 to 1.0.1

Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 0.34.1 to 1.0.1.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.0.1/packages/vitest)

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

build(deps-dev): bump @types/node from 20.10.2 to 20.10.3

Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 20.10.2 to 20.10.3.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

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

EIP4844: Add single minimal e2e test.

Change output cannon game type to 1

feat: Fix Foundry Update to reset Git Repo

feat(ctb): `OutputBisectionGame`

Merge pull request #8414 from ethereum-optimism/dependabot/go_modules/github.com/urfave/cli/v2-2.26.0

build(deps): bump github.com/urfave/cli/v2 from 2.25.7 to 2.26.0

ctb: Fix multithreaded test race

Load the split depth from the contract when creating output_cannon games
Increase the max game depth so the cannon trace completes.
Legacy cannon games now have a fixed depth of 30 to avoid making those tests even slower.
Fix extra data creation in e2e helpers so the l2 block number is set correctly.

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

Co-authored-by: Adrian Sutton <adrian@oplabs.co>

chores

op-node: batch_decoder: Support Span Batch

Bumps [github.com/urfave/cli/v2](https://github.com/urfave/cli) from 2.25.7 to 2.26.0.
- [Release notes](https://github.com/urfave/cli/releases)
- [Changelog](https://github.com/urfave/cli/blob/main/docs/CHANGELOG.md)
- [Commits](https://github.com/urfave/cli/compare/v2.25.7...v2.26.0)

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

`generate-l2-genesis.sh` is causing spurious test failures. The `.testdata/genesis.json` file comes up as zero-length in tests, even when the script checks for its length before exiting. I believe this is because multiple processes are executing the `generate-l2-genesis.sh` file at once, which causes a race condition where different invocations of the script cause the genesis file to be truncated.

This PR attempts to fix the issue by using a temporary directory as a lock to prevent multiple invocations of the `generate-l2-genesis.sh` script from running at the same time. Directory creations are atomic in Bash, so we can use this technique to create a mutex. If the directory can't be created, then the script will assume that another script is writing the genesis file and wait up to 5 minutes for it to be created. The script uses `trap` to delete the mutex directory when it's done.

op-e2e: Minor cleanups

op-e2e: Actually kill geth on shim termination

The shim creates a new op-geth process, which was not being killed when the shim itself was killed. This prevented termination signals from the test process from propagating to op-geth, which left orphan processes hanging around. Turns out that not a single op-geth process was being explicitly terminated.

Was looking at op-e2e flakes today and found a couple of minor fixes:

- The op-e2e-ext-geth test sometimes flakes because Geth is still writing to its datadir while it's being cleaned up. You can see an example of this [here](https://app.circleci.com/pipelines/gh/ethereum-optimism/optimism/32316/workflows/3cc82541-6770-4ded-b842-05e1cd5ae0ee/jobs/1499210). This PR adds a separate mechanism to create and clean up temporary directories in E2E tests that doesn't fail the test of the directory is written to while it's being cleaned up.
- The bridge test doesn't check for iterator errors. This masks the root cause of the flakes in this test.

Fix one typo

Renames the FAULT game type to CANNON.
Removes the VALIDITY and ATTESTATION game types.

Update run-challenger.md

Merge pull request #8395 from ethereum-optimism/dependabot/npm_and_yarn/testing-library/jest-dom-6.1.5

build(deps-dev): bump @testing-library/jest-dom from 6.1.4 to 6.1.5

Here are the identified typos and suggested corrections I have:

   In Prerequisites:
        "concreate" should be "concrete."

   In Starting op-challenger:
      
        "Run the challenger with these placeholders set." I rephrased it to "Run the challenger after setting these placeholders" for the sake of clarity.