fix one typo

proxyd: Delete bad test

contracts-bedrock: add base sepolia deploy config

contracts-bedrock: fix pgn sepolia config

This test was originally checking for a panic in the websocket code. However, we have since re-architected this code and have coverage for this issue elsewhere. Therefore, this test is now superfluous and can be removed. It causes a lot of spam in the logs, and makes debugging other tests harder.

contracts-bedrock: zora-sepolia deploy config

contracts-bedrock: L2OutputOracle deployment

Updates the deploy config for pgn sepolia to
be conformant to the deploy config spec. Not sure why
CI is passing as the go code is supposed to check for
non compliant deploy config. It is likely because the solidity
and the go got out of sync. We could use a rethinking of how
we do deploy config. Ideally the entire thing can be simplified
now that deploy config contains op stack chain specific config,
superchain target specific config and also config values that
go into L1 and also config values that go into L2.

This change wouldn't be necessary if the lazy deploy config change
https://github.com/ethereum-optimism/optimism/issues/7711 was
implemented. It was attempted https://github.com/ethereum-optimism/optimism/pull/7776
but became stale and added a lot of overhead.

fix(multisig-mon): add onepass cli to dockerfile

Make it pass config checking

Adds the deploy config for `zora-sepolia`. This was sourced from
conduit. This is required to deploy the new L2OutputOracle contract.

Related to https://github.com/ethereum-optimism/optimism/pull/8499

feat(op-challenger): Prestate Provider Refactor

feat(ctb): `OutputBisectionGame` test refactor + fixes

Deploys the latest implementation of the `L2OutputOracle` to sepolia
and commits the artifact.

The following script was used for the deployment.

```bash

export IMPL_SALT="op/acc"

forge script scripts/Deploy.s.sol:Deploy \
  --sig 'deployL2OutputOracle()' --rpc-url $ETH_RPC_URL \
  --private-key $PRIVATE_KEY \
  --broadcast \
  --verify
```

https://sepolia.etherscan.io/address/0x83aeb8b156cd90e64c702781c84a681dadb1dde2

Sources the deploy config from https://github.com/base-org/contract-deployments/blob/main/sepolia/2023-09-26-deploy/deploy-config/deploy-config.json
We need to double check that this is up to date, ie it is possible that
some config has changed over time. The problem variables that we care
about from within this config are the constructor args to the
L2OutputOracle:

- cfg.l2OutputOracleSubmissionInterval
- cfg.l2BlockTime
- cfg.l2OutputOracleProposer
- cfg.l2OutputOracleChallenger
- cfg.finalizationPeriodSeconds

If any of these values changed, they should be caught by the state diff
tests written in `superchain-ops` for performing the upgrade.

This deploy config is required to deploy a new L2OutputOracle
implementation for Base Sepolia as part of the Extended Pause Upgrade.

contracts-bedrock: deploy superchain config

Both the proxy and the latest implementation.
Deploy them to sepolia. The proxy was deployed with
the following command:

```bash
forge script scripts/Deploy.s.sol:Deploy \
  --sig 'deployERC1967Proxy(string)' --rpc-url $ETH_RPC_URL \
  --private-key $PRIVATE_KEY \
  --broadcast \
  --verify \
  SuperchainConfigProxy

```

build(deps): bump actions/setup-python from 4 to 5

op-e2e: Add test utility to wait for balance changes

Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](https://github.com/actions/setup-python/compare/v4...v5)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-type: direct:production
  update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>

fix(ufm): gracefully handle failed tx creation

This PR adds a utility to wait for an address's balance to change. The utility checks for the balance change for two minutes, and returns the new value once it changes. It rreturns an error on timeout.

Some tests - particularly the ext-geth tests - are failing because balance changes that we expect to occur are not. My hunch is that this may be related to a race condition somewhere between the test code and op-geth, but I can't be sure. By waiting for the balance to change, we can eliminate spurious race conditions and see if this is related to some other underlying issue.

feat(op-challenger): Output Bisection Game Genesis Output Root Fetching

build(deps): bump @sentry/node from 7.84.0 to 7.85.0

providers.

fix(op-challenger): genesis output root validation for top of output bisection games

genesis output root test

fix(op-challenger): revert validation wiring

revert newline change

contracts-bedrock: simplify storage setting in SuperchainConfig