The following warning was happening in CI:

```
(node:11982) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
```

Simply replaces the `rmdir` with `rm`. Note that the `sync` methods
are used here instead of the async promise based methods.

* feat: basic plasma da server

* catch all not found errors

* feat: switch to minio and file server

* add file

* fix: handle feedback

* fix: tidy

* fix: tidy mods again

* chore: add S3 config info

* contracts-bedrock: update weth98

The custom gas token project is moving away from using
the original weth9 code as a predeploy to using the
weth98 code as a predeploy. As part of this, the ability
to override the name and symbol are required for chains
that use a custom gas token. There is no way to
mark an inline declaration as `virtual`, it requires
moving to a `function` syntax. Definitely less clean
looking but necessary to support the override ability.

The implementation of the new WETH predeploy is as follows:

```solidity
contract WETH is WETH98 {
    /// @notice Returns the name of the token from the L1Block contract
    function name() external view override returns (string memory) {
        return string.concat("Wrapped ", L1Block(Predeploys.L1_BLOCK_ATTRIBUTES).gasPayingTokenName());
    }

    /// @notice Returns the symbol of the token from the L1Block contract
    function symbol() external view override returns (string memory) {
        return string.concat("W", L1Block(Predeploys.L1_BLOCK_ATTRIBUTES).gasPayingTokenSymbol());
    }
}
```

Where when not in custom gas token mode, it with return `Wrapped Ether`
and `WETH`, so it is backwards compatible.

This commit also adds a fallback function since the original weth9 has
a fallback function but this one does not. While the receive function
can work, adding the fallback function ensures that the same behavior
as weth9 is achieved when making a call that includes calldata + value.

* contracts-bedrock: fix compile

* snapshots: update

* op-bindings: regenerate

* contracts-bedrock: cleanup weth98

* contracts-bedrock: semver lock

* contracts-bedrock: weth98 tests

* lint: fix

* removing out of date note

* removing accidental commit

Bumps [wagmi](https://github.com/wevm/wagmi/tree/HEAD/packages/react) from 2.5.5 to 2.5.19.
- [Release notes](https://github.com/wevm/wagmi/releases)
- [Changelog](https://github.com/wevm/wagmi/blob/main/packages/react/CHANGELOG.md)
- [Commits](https://github.com/wevm/wagmi/commits/wagmi@2.5.19/packages/react)

---
updated-dependencies:
- dependency-name: wagmi
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [@swc/core](https://github.com/swc-project/swc) from 1.4.6 to 1.4.13.
- [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.4.6...v1.4.13)

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

* contracts-bedrock: update solady imports

Without this commit, there are import issues based on some
solady imports being prefixed with `@` and some not. `lib-keccak`
has a remapping for solady with the `@` prefix and this commit
updates `contracts-bedrock` to use a remapping with `@` prefix
to solady imports.

Without a recursive git submodule init, it is not possible to
build without this change. We should also be sure of the exact version
of solady that we are using if we are running it in production code.

* op-bindings: update

* ctb: semver lock

* ctb: cleanup, bump fdg version

* op-bindings: regen

* semver: update

Move away from using the fallback function on weth9 towards instead
using the explicit deposit method. This is to reduce diff with the
custom gas token project, just a very small change.

The weth98 contract doesn't have a fallback function, if it did
then this change would not be required.

Bumps [typescript](https://github.com/Microsoft/TypeScript) from 5.3.3 to 5.4.5.
- [Release notes](https://github.com/Microsoft/TypeScript/releases)
- [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release.yml)
- [Commits](https://github.com/Microsoft/TypeScript/compare/v5.3.3...v5.4.5)

---
updated-dependencies:
- dependency-name: typescript
  dependency-type: direct:development
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* op-node: fix ecotone upgrade test

Previously the upgrade transactions test made an assertion against
the bytecode that is in the bindings. This needs to be modified
because the upgrade txs cannot ever change as they are part of
consensus. Any modification to the bindings means that the assertion
will fail. We should test against the expected value directly
instead of going through the binding that has no guarantee
to be on a particular version and will change over time.

* op-node: fix test

* fix: set version during build process for op-node,batcher,proposer

* fix: use git tag --points-at flag instead of --contains when setting version

* fix: prioritize release tag over -rc tags

* ctb: Add events and custom errors to LivenessModule

ctb: Use same event as Safe contract

* ctb: Used past tense event name OwnershipTransferredToFallback()

Signed-off-by: sellskin <mydesk@yeah.net>

semver

autogens

* Add iterative batch building benchmark

* Embed Compressor Logic directly to Span Channel Out

* PR Comments

* Tests

* fix error handling

* remove errant comment

* PR Comments

* handle Read more correctly

* similar for Write

* update geth dependency to version with upstream updates to v1.13.11

* fix op-program tests

* update op-geth dep to tagged commit

* Store cannon-go-lint-and-test logs on failure

Needed to debug why this test is failing

* Update config.yml

* Update config.yml

* Try without coverage

* Update config.yml

* Update config.yml

* Update .circleci/config.yml

Bumps [h2](https://github.com/hyperium/h2) from 0.3.24 to 0.3.26.
- [Release notes](https://github.com/hyperium/h2/releases)
- [Changelog](https://github.com/hyperium/h2/blob/v0.3.26/CHANGELOG.md)
- [Commits](https://github.com/hyperium/h2/compare/v0.3.24...v0.3.26)

---
updated-dependencies:
- dependency-name: h2
  dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* op-upgrade: delete dead version

Deletes the `op-upgrade-mcp` binary in favor of the `op-upgrade` binary.
This enables us to leverage the `superchain-regsitry` without needing to
hardcode addresses in one off locations.

`op-upgrade-mcp` existed because `superchain-regsitry` assumes that
there are implementations that can be shared between networks, ie
post MCP world, meaning there are no immutables in the code that
are network specific.

* op-upgrade: apply superchain config to L1 upgrade work, e.g. to source superchainConfig.Config.SuperchainConfigAddr for L1CrossDomainMessenger

---------
Co-authored-by: protolambda <proto@protolambda.com>

The old 2 minute timeout is no longer sufficient. As cannon
execution sometimes requires more time to generate traces.

* contracts-bedrock: fix deploy config for mainnet MCP upgrade

The config param for the scalar was not updated in the
deploy config when it was changed on chain. If we can enforce
that the deploy config is always used as the source of truth
for when doing on chain config changes, it can help to scale
the team as other teams can use the same config file and know
that the values in there represent the truth. This is a fundamental
problem with the `initialize` pattern, we need to move away from
it eventually.

The deploy config is updated with the value that is used on
mainnet and the parsing is updated to handle the new ecotone
style config, which tightly packs the values into a single
bytes32.

* op-chain-ops: more cleanup

* op-e2e: fix build

* cleanup: modularize scalar encoding and decoding

Ensures that the same consensus code is used
to encode and decode the scalar in various places.

* op-chain-ops: fix L2 genesis generation

* config: fix serialization

* op-chain-ops: refactor config

Make backwards compatible

* op-chain-ops: fix build

* deploy-config: update mainnet fee scalar config

Should match mainnet values

* op-chain-ops: fix test

* genesis: test L1Block predeploy state setting

* op-upgrade: delete dead code

* build: fix

* op-chain-ops: add deprecation warning
Co-authored-by: Sebastian Stammler <seb@oplabs.co>

* deploy-config: use mainnet values
Co-authored-by: Sebastian Stammler <seb@oplabs.co>

* deploy-config: use mainnet values
Co-authored-by: Sebastian Stammler <seb@oplabs.co>

* op-service: end to end encode/decode scalar tests

* tests: cleanup

* op-chain-ops: fix nits, adapt to breaking simulated backend changes

* op-chain-ops: fix comment and address-type conversion nits

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

Bumps [nx](https://github.com/nrwl/nx/tree/HEAD/packages/nx) from 18.1.2 to 18.2.2.
- [Release notes](https://github.com/nrwl/nx/releases)
- [Commits](https://github.com/nrwl/nx/commits/18.2.2/packages/nx)

---
updated-dependencies:
- dependency-name: nx
  dependency-type: direct:development
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* use updated op-geth

* update geth moar

* resource usage cleanup

* remove sleeping

* go: fix broken indirect dependency of github.com/kataras/iris/v12

* proxyd: update to geth v1.13.10

* proxyd: update to geth v1.13.14

* op-chain-ops: reduce diff, utilize chainID from caller to make Permit2 path use correct chainID during deployment

* op-chain-ops: L2 backend only, enable shanghai/canyon by default, fix doc comments

* op-chain-ops: simulator without L2 features, to support op-upgrade

---------
Co-authored-by: protolambda <proto@protolambda.com>

Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.1.5 to 5.1.7.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.1.7/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.1.7/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Add ASTERISC dispute game type

* Use pre-funded account for local devnet deployer

* Add op-program-client-riscv build command

* Add comment about deployer account

This reverts commit 3c34770c.

* ci-builder: add yq

Adds `yq` to `ci-builder` so that we can read the yaml information
inside of the superchain registry.

`yq` is `jq` but for yaml, see https://github.com/mikefarah/yq

* hardcode yq version
Co-authored-by: Joshua Gutow <jgutow@oplabs.co>

* hardcode gotestsum version
Co-authored-by: Joshua Gutow <jgutow@oplabs.co>

---------
Co-authored-by: Joshua Gutow <jgutow@oplabs.co>

Bumps google.golang.org/protobuf from 1.32.0 to 1.33.0.

---
updated-dependencies:
- dependency-name: google.golang.org/protobuf
  dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* feat(op-dispute-mon): track claims resolved against honest actors

* fix(op-dispute-mon): break after honest actor error is logged

* fix(op-dispute-mon): lints

* feat(op-dispute-mon): resolution status

* fix(op-dispute-mon): merge fixes

feat(indexer): Remove goerli config options. Specify DisputeGameFactoryProxy address OP Sepolia (#10032)

* remove goerli. add dpf for optimism sepolia

* remove more goerli references & unit tests

* address etl log inactivity

* Update indexer/README.md
Co-authored-by: Will Cory <willcory10@gmail.com>

---------
Co-authored-by: Will Cory <willcory10@gmail.com>