Now that we don't use the kurtosis cli, there's no reason to go
through the filesystem to pass a configuration file.

This change reimplements run over the kurtosis SDK instead of shelling
out to the CLI tool, which fixes potential consistency problems with
other uses of the SDK.

Additionally, we split the endpoint detection logic into a separate
entity (will make it a separate package a bit later), and improve the
host handling part by no longer assuming reachability on localhost
(implicitly assuming Docker backend). This is a step toward supporting
k8s backend transparently.

* feat: remove enableLegacyContracts

* feat: remove setUseFaultProofs

* feat: Remove useFaultProofs branch in Deploy._run()

* gas snapshot

* feat: remove useFaultProofs

* Revert "op-batcher: Fix concurrent map write (#13527)"

This reverts commit 90435d07.

* lock channelMgrMutex during recordFailedDARequest

* rename / export pruneSafeBlocks and pruneChannels

mtx on channel_manager too

This prepares the ground for op-challenger needing a URL locator
serving prestate proof files.

A {{localPrestate}} placeholder will expand to a URL that's usable by
op-challenger.

* [op-program] Update releases.json

* [op-program] Tweak verify formatting

This ties together the various capabilities in pkg/ and orchestrates them. The phases are:
- build local artifacts per input template specification
- put them where they can be accessed at runtime by kurtosis
- run the deployment
- collect useful information and output it for downstream consumption

Also provide sample devnet definitions

Those are just starting points. We'll need to come up with definitions
that actually make sense.

Note that there is a temporary workaround for op-deployer image:

We need http locator support, which has been merged into op-deployer,
but the current version at HEAD doesn't quite work with kurtosis yet.

We'll fix that separately, at which point we'll be able to point to a
localDockerBuild of "op-deployer" just as well, if we want to.

* ct/scripts/ChainAssertions: add require revert message
Signed-off-by: jsvisa <delweng@gmail.com>

* ct/scripts/deploy/Deploy: add require revert message
Signed-off-by: jsvisa <delweng@gmail.com>

* ct/scripts/deploy/DeployOwnership: add require revert message
Signed-off-by: jsvisa <delweng@gmail.com>

* ct/scripts/deploy/DeployPeriphery: add require revert message
Signed-off-by: jsvisa <delweng@gmail.com>

* feat(semgrep): enable for all solidity files, except WETH9
Signed-off-by: jsvisa <delweng@gmail.com>

* fix require issues
Signed-off-by: jsvisa <delweng@gmail.com>

* fix(semgrep): run just semgrep to fix the require rules
Signed-off-by: jsvisa <delweng@gmail.com>

---------
Signed-off-by: jsvisa <delweng@gmail.com>

Co-authored-by: Tarun Khasnavis <tarunkhasnavis@Taruns-MacBook-Pro.local>

Added in extra dependency details to the getting started versions script to point people to where to learn more. (#13540)

* attempt...

* fixes

* fix checks

* fix kontrol build

* update DeploymentSummaryFaultProofs kontrol hash

* fixes

* undo unnecessary change

* feat: Reduce diff and usage of OptimismPortal2

* semver

* fix: init test

---------
Co-authored-by: Maurelian <maurelian@protonmail.ch>

* op-proposer: do not propose if outputRoot is the same as last proposed game

* fixed porposer tests

* PR comments

* Fix log message.

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

This handles deploying the kurtosis enclave according to spec, and
then stitching together the relevant information to be transmitted for
downstream consumption.

* feature: Allow adding arbitrary HTTP handlers to RPC HTTP Server.

* feature: Add sync package to handle streaming db files between nodes.

* tweak: Add DB sync server handler to op-supervisor server.

* feature: Use db sync if it's configured and there's no existing db.

* tweak: Use retry lib, which also adds max retries.

* rename: SyncRPC -> SyncEndpoint.

* tweak: Make the initial chain set part of the Server constructor.

* cleanup: Remove unused functions.

* rename: client -> syncClient to avoid package collision.

* fix: Load DepSet and use for sync server.

* tweak: Use client.BasicHTTPClient for sync client.

* fix: Don't double concat the path.

* tests,fix: Set sync resume to true.

* tweak: Add error context.

* tweak: Make http body close lint-friendly.

* tweak: Change retry policy to backoff from 1s to 30s, up to 10 minutes.

* tests,fix: Use require.ErrorIs to handle wrapped error.

This is in service of outputting useful information at the end of the
deployment.

Here we get back some useful wallets and addresses for downstream
consumption.

This enables us to retrieve information about artifacts and services,
for downstream consumption.

* Update README.md

* Update README.md

* op-supervisor: fix typo in README.md

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

This can be used in isolation to sanity check that a kurtosis-devnet
template expands properly, without having to run the entire workflow
(although it would fail early anyway).

* fix: more robust opcm checking upon deploy.

* Update packages/contracts-bedrock/scripts/deploy/ChainAssertions.sol
Co-authored-by: Maurelian <john@oplabs.co>

* Update packages/contracts-bedrock/scripts/deploy/ChainAssertions.sol
Co-authored-by: Maurelian <john@oplabs.co>

* fix: pr comments.

---------
Co-authored-by: Maurelian <john@oplabs.co>

This will allow us to point kurtosis to these artifacts, and deploy
them from HEAD.

Right now I'm assuming we have some available "just" recipes for them.
We might decide to do things differently down the road.

* feat: Move OptimismMintableERC721 and Factory contracts to L2 dir

* feat: Remove outdated comment about 721 bridge refunds.

Either we deleted that code path, or it never existed in the 721 bridge
and we just copy pasted the comment form the ERC20 bridge.

* fix: semver

* op-program: Support multiple types of op-program releases

* include type in formatted release string

* show label on fault

* also show label for onExit

Our docker builds can be published to the local registry, so kurtosis
can access them.

We need something similar for contracts bundles for now. We'll bring
up a local http server for the duration of the kurtosis command run,
which will serve the contracts.

This enables us to parse the input provided to kurtosis for the
enclave creation, and retrieve some basic information to organize the
dynamic information we'll get from the enclave directly.

Namely, the name and network ID for each chain created.

We need a few things:
- some convenience functions for expanding user functions
- optional data to drive the template
- strict expansion (missingkley=error)

The artifacts for v1.8.0 were generated from the tag `op-contracts-v180-artifacts-base`, which points to `proposal/contracts/v1.8.0` with the non-proxied OPCM backported.

The OPCM was deployed using the `opcm bootstrap` command. The PDG blueprints were updated using a custom script which you can find at the `op-contracts-v180-blueprints-script` [tag](https://github.com/ethereum-optimism/optimism/commit/a7091185a787ea104343abafc311d65a5916e4b8).

As part of this PR, I also added a bunch of tests to assert that the semver versions of deployed contracts are correct. I'll add similar tests for mainnet once the gov vote passes.

* feat: Rename Upgrade.s.sol to ForkProd.s.sol

The updated name is more descriptive of what the code currently does. It
also reflects more accurately the current plan of applying the upgrade
outside of this script in a separate one, which may be named
`Upgrade.s.sol` and  will call `OPCM.upgrade()`.

* feat: fix artifcat name

* feat: ForkLive instead of ForkProd

* prefer .FillBytes() to .Bytes() and copy

The latter can result in an error if the number is less than 32 bytes in length (it gets padded incorrectly).

* add tests

* output to JSON

* add test case for OPM

* tidy up

* use const in test

* op-service: RPC subscribe interface fix and utils

* op-service: fix subscribe args pass through