Delete `pnpm prepare` step from Makefile as this script has been removed recently

Just some regular README cleanup. Nothing huge here, a few tweaks
to make things flow smoothly.

* fix version

* change to suggestion

* Alt-DA: Add aliases to cli for Alt-DA

* replace "plasma mode" with "alt-da mode"

* plasma: Split commitments & challenges

This splits the current two queues into four queues. Two for commitments
and two for challenges. Challenges are commitments are split because they
are different things. Each has two physical queues to differentiate between
items which have not expired and items which have expired but not finalized.

This also splits the commitment origin from the challenge origin because the
challenge origin can advance independently of the commitment origin.

* Cleanup Refactor ; Fix Tests

Reading over the refactor and understanding it for myself,
I made some organizational edits, and fixed an issue in the E2E tests.

* remove commented assert

* Update op-plasma/damgr.go
Co-authored-by: Adrian Sutton <adrian@oplabs.co>

* add warn log for DA Server Not Found errors

---------
Co-authored-by: axelKingsley <axel.kingsley@gmail.com>
Co-authored-by: Adrian Sutton <adrian@oplabs.co>

* challenger: Create generic vm executor and use for asterisc

* challenger: Move executor utils to vm package

* challenger: Switch cannon to use common vm executor.

* challenger: Use vm.Config to encapsulate Cannon config items.

* challenger: Rename to include Path

* challenger: Use vm.Config to encapsulate Asterisc config items.

* challenger: Remove unused interface

* challenger: Reduce amount of config passed to cannon/asterisc trace providers

* challenger: Remove Config from names

* challenger: Remove replaced cannon metrics

* contracts: Make L2 genesis script configurable

* contracts: Read latest fork from deploy config in L2 genesis script

* contracts: add README entry for new L2 genesis script env vars

* address review

* output oldest l1 origin in channel

* also log l2 range when channel close

* use eth.ToBlockID

* fix a bug

* add testcase for 3 new fields

* op-chain-ops: cleanup genesis check

Ensures that the check for contracts are correct based on the
config flags instead of always skipping the fault proof contracts
in the check.

* config: fix

Removes the `sdk-next` tests from CI. The sdk no longer lives
in the protocol monorepo, it lives in the ecosystem monorepo now,
see https://github.com/ethereum-optimism/ecosystem.

Delete `husky` and `lint-checked` from the monorepo as no
active JS development happens here. There is no need to run the
pre commit lint hook on every single commit, this only slows down
the latency of all commits.

Bumps [github.com/DataDog/zstd](https://github.com/DataDog/zstd) from 1.5.2 to 1.5.5.
- [Release notes](https://github.com/DataDog/zstd/releases)
- [Commits](https://github.com/DataDog/zstd/compare/v1.5.2...v1.5.5)

---
updated-dependencies:
- dependency-name: github.com/DataDog/zstd
  dependency-type: direct:production
  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 [github.com/hashicorp/raft](https://github.com/hashicorp/raft) from 1.6.1 to 1.7.0.
- [Release notes](https://github.com/hashicorp/raft/releases)
- [Changelog](https://github.com/hashicorp/raft/blob/main/CHANGELOG.md)
- [Commits](https://github.com/hashicorp/raft/compare/v1.6.1...v1.7.0)

---
updated-dependencies:
- dependency-name: github.com/hashicorp/raft
  dependency-type: direct:production
  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>

Removes the SDK and adds a small temporary package that houses
the two Hardhat tasks that the bedrock-devnet relies on. It's
generally much nicer to have a dedicated place for the SDK in the
ecosystem repository rather than having it exist in two places
awkwardly simply because of these two tasks.

Bumps [github.com/minio/minio-go/v7](https://github.com/minio/minio-go) from 7.0.70 to 7.0.71.
- [Release notes](https://github.com/minio/minio-go/releases)
- [Commits](https://github.com/minio/minio-go/compare/v7.0.70...v7.0.71)

---
updated-dependencies:
- dependency-name: github.com/minio/minio-go/v7
  dependency-type: direct:production
  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>

* adding timestamp for blocks checked and highest, so we can monitor how long ago the block we are using was produced

* adding logs for connecting disputeGame with withdrawalHash

* imporved logs

* adding details on logs for wd-mon and faultproof-wd-mon

* adding extra information for wd-mon also for valid withdrawal

* Update packages/chain-mon/src/wd-mon/service.ts
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* Update packages/chain-mon/src/faultproof-wd-mon/service.ts
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* fixing object

* improved logs and metrics for wd mon

* added extra logging information and fixing bugs on initial block number

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

Remove trianglesphere

* dependabot(gomod): bump golang.org/x/crypto from 0.23.0 to 0.24.0

Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.23.0 to 0.24.0.
- [Commits](https://github.com/golang/crypto/compare/v0.23.0...v0.24.0)

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

* deps: update

---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Mark Tyneway <mark.tyneway@gmail.com>

Fixes the following compiler warning:

```
Compiler run successful with warnings:
Warning (2018): Function state mutability can be restricted to view
  --> test/periphery/drippie/dripchecks/CheckBalanceLow.t.sol:20:5:
   |
20 |     function test_name_succeeds() external {
   |     ^ (Relevant source part starts here and spans across multiple lines).

Warning (2018): Function state mutability can be restricted to view
  --> test/periphery/drippie/dripchecks/CheckGelatoLow.t.sol:45:5:
   |
45 |     function test_name_succeeds() external {
   |     ^ (Relevant source part starts here and spans across multiple lines).

Warning (2018): Function state mutability can be restricted to view
  --> test/periphery/drippie/dripchecks/CheckSecrets.t.sol:30:5:
   |
30 |     function test_name_succeeds() external {
   |     ^ (Relevant source part starts here and spans across multiple lines).

Warning (2018): Function state mutability can be restricted to view
  --> test/periphery/drippie/dripchecks/CheckTrue.t.sol:19:5:
   |
19 |     function test_name_succeeds() external {
   |     ^ (Relevant source part starts here and spans across multiple lines).
```

This should be caught in CI, not sure why it wasn't