Allow for the addresses used in the deploy script to be defined
by a JSON file at the the path defined by the `ADDRESSES` environment
variable. This makes the deploy script easy to use when it comes to
composing with the `superchain-registry`. Just set the `ADDRESSES`
env var to the path on the local filesystem that points to the
`extra/addresses/<network>/<l2>.json` file. See the
[example](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/extra/addresses/mainnet/op.json) here.

This gives a path forward for deprecating the concept of `deployments`
in the `contracts-bedrock` package. We really only use the `deployments`
directory for getting contract addresses. We want a single source of
truth for contract addresses which is `superchain-registry`. Using this
env var allows the deploy script to easily compose with
`superchain-registry`.

`ffi` and `jq` are used instead of `vm.readFile` to break out of the
security properties that foundry uses, we do not want to need to specify
all possible directories on the filesystem as readable in the
`foundry.toml`

contracts-bedrock: deploy OptimismMintableERC20Factory sepolia

build(deps-dev): bump @wagmi/core from 1.4.8 to 1.4.10

contracts-bedrock: deploy OptimismPortal extended pause

fix one typo

proxyd: Delete bad test

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

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

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

OP sepolia OptimismMintableERC20Factory deployment

Using the following command:
```

export IMPL_SALT="op/acc"
export ADDRESSES=/Users/tynes/Projects/github.com/ethereum-optimism/superchain-registry/superchain/extra/addresses/sepolia/op.json

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

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