feat(eigenda): EigenDA M0 (#3650)

## What ❔
This PR extracts the eigenda client into a separate crate and adds new
metrics for the grafana dashboard. Completing M0 milestone.
<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- The `Why` has to be clear to non-Matter Labs entities running their
own ZK Chain -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Is this a breaking change?
- [ ] Yes
- [x] No

## Operational changes
<!-- Any config changes? Any new flags? Any changes to any scripts? -->
<!-- Please add anything that non-Matter Labs entities running their own
ZK Chain may need to know -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zkstack dev fmt` and `zkstack dev
lint`.

---------

Co-authored-by: Juan Munoz <juanmunoz890@gmail.com>
Co-authored-by: juan518munoz <62400508+juan518munoz@users.noreply.github.com>
Co-authored-by: Juan Bono <juanbono94@gmail.com>

Author: 3 people

core/Cargo.lock

@@ -230,11 +230,7 @@ tonic = { version = "0.11.0", default-features = false }
 pbjson-types = "0.6.0"
 
 # Eigen
-tokio-stream = "0.1.16"
-rust-kzg-bn254 = "0.2.1"
-ark-bn254 = "0.5.0"
-num-bigint = "0.4.6"
-serial_test = { version = "3.1.1", features = ["file_locks"] }
+rust-eigenda-client = "0.1.1"
 
 # Here and below:
 # We *always* pin the latest version of protocol to disallow accidental changes in the execution logic.

core/Cargo.toml

@@ -15,6 +15,7 @@ ignore = [
     "RUSTSEC-2021-0145",
     "RUSTSEC-2021-0139",
     "RUSTSEC-2024-0388", # `derivative` is unmaintained, crypto dependenicies (boojum, circuit_encodings and others) rely on it
+    "RUSTSEC-2024-0436", # `paste` is an unmaintained dependency of various crates (like alloy-primitives, sqlx-core)
 ]
 
 [licenses]

core/deny.toml

@@ -56,18 +56,4 @@ tonic = { workspace = true, features = ["tls-roots", "prost", "codegen"] }
 pbjson-types.workspace = true
 
 # Eigen dependencies
-tokio-stream.workspace = true
-rand.workspace = true
-sha3.workspace = true
-tiny-keccak.workspace = true
-ethabi.workspace = true
-rust-kzg-bn254.workspace = true
-ark-bn254.workspace = true
-num-bigint.workspace = true
-zksync_web3_decl.workspace = true
-zksync_eth_client.workspace = true
-thiserror.workspace = true
-tempfile.workspace = true
-
-[dev-dependencies]
-serial_test.workspace = true
+rust-eigenda-client.workspace = true

core/node/da_clients/Cargo.toml

@@ -3,35 +3,3 @@
 EigenDA is as a high-throughput data availability layer for rollups. It is an EigenLayer AVS (Actively Validated
 Service), so it leverages Ethereum's economic security instead of bootstrapping a new network with its own validators.
 For more information you can check the [docs](https://docs.eigenda.xyz/).
-
-## Temporary
-
-In order to implement the integration we generated some `.proto` files from EigenDA repo that were compiled using the
-following function:
-
-```rust
-pub fn compile_protos() {
-    let fds = protox::compile(
-        [
-            "proto/common.proto",
-            "proto/disperser.proto",
-        ],
-        ["."],
-    )
-    .expect("protox failed to build");
-
-    tonic_build::configure()
-        .build_client(true)
-        .build_server(false)
-        .skip_protoc_run()
-        .out_dir("generated")
-        .compile_fds(fds)
-        .unwrap();
-}
-```
-
-The generated folder is considered a temporary solution until the EigenDA has a library with either a protogen, or
-preferably a full Rust client implementation.
-
-proto files are not included here to not create confusion in case they are not updated in time, so the EigenDA
-[repo](https://github.com/Layr-Labs/eigenda/tree/master/api/proto) has to be a source of truth for the proto files.