uses the `eip7732-support` branch from dora:
https://github.com/ethpandaops/dora/pull/227

- Awaiting a genesis generator update to consume these values

bump the memory limit for assertoor to 8GB

increasing the limit is necessary to run child processes (like the
execution spec tests) reliable.
the limit is for the whole container, which not only includes assertoor,
but also all sub-processes launched by tests.

The root folder `/` is not writable when running as non-root user, so we
move the db to the /app folder

This PR elaborates what the `snooper_elabed` flag does.

It was missing a leading 0.

Co-authored-by: pk910 <philipp@pk910.de>
Co-authored-by: pk910 <github@pk910.de>

This PR replaces [goomy](https://github.com/ethpandaops/goomy-blob) with
[spamoor](https://github.com/ethpandaops/spamoor).

The spamoor project is based on goomy, but was improved a lot to handle
high transaction throughput reliably.
It supports all features that goomy provides, but blob scenarios are
prefixed with `blob-`.

As spamoor works much better by now, it makes sense to deprecate goomy
and replace it with spamoor.

Signed-off-by: Barnabas Busa <barnabas.busa@ethereum.org>

`electra-support` as been merged into master and a new release is
available too.

Signed-off-by: Barnabas Busa <barnabas.busa@ethereum.org>

Signed-off-by: Barnabas Busa <barnabas.busa@ethereum.org>

Prysm added QUIC to their client as per
https://github.com/prysmaticlabs/prysm/pull/14688 . This currently broke
our runs using the master branch prysm image due to the QUIC port
running on 13000 by default. Which was conflicting with the settings we
were providing for the UDP port:

```sh
--p2p-quic-port value                                The QUIC port used by libp2p. (default: 13000)
--p2p-tcp-port value                                 The TCP port used by libp2p. (default: 13000)
--p2p-udp-port value                                 The UDP port used by the discovery service discv5. (default: 12000)
```

I've also added the CLI flags for it, but still commented out until a
stable release is done.

Signed-off-by: Barnabas Busa <barnabas.busa@ethereum.org>

Depends on
https://github.com/ethpandaops/eth-client-docker-image-builder/pull/208
Depends on https://github.com/flashbots/rbuilder/pull/237

---------
Signed-off-by: Barnabas Busa <barnabas.busa@ethereum.org>

Signed-off-by: Barnabas Busa <barnabas.busa@ethereum.org>

fix #837 
the default blockscout image version does not work on my machine. 
so i added the blockscout_params for blockscout service. now user can
customize the image versions they want to use.
it contains two params:
```yaml
blockscout_params:
  # blockscout docker image to use
  # Defaults to the latest image
  image: "blockscout/blockscout:latest"
  # blockscout smart contract verifier image to use
  # Defaults to ghcr.io/blockscout/smart-contract-verifier:v1.9.0
  verif_image: "ghcr.io/blockscout/smart-contract-verifier:v1.9.0"
```

i already tested it on my machine and it worke well.

---------
Co-authored-by: Barnabas Busa <barnabas.busa@ethereum.org>
Co-authored-by: Barnabas Busa <busa.barnabas@gmail.com>

This PR has 2 commits:
- Use different ports for gRPC and HTTP communication between Prysm VC
and BN
- Switch gRPC and HTTP ports to be consistent with default values.

Before this PR, we had this issue:

```
 docker inspect vc-1-geth-prysm--773bda94114946f3b501f3e293517426
[
    {
        "Id": "93713c8d7020aeb505836a11a1858e27dd9ecac19e7e7ed4814f677c30bc9c48",
        "Created": "2024-11-29T13:05:02.300408215Z",
        "Path": "/validator",
        "Args": [
            "--accept-terms-of-use=true",
            "--chain-config-file=/network-configs/config.yaml",
            "--suggested-fee-recipient=0x8943545177806ED17B9F23F0a21ee5948eCaa776",
            "--disable-monitoring=false",
            "--monitoring-host=0.0.0.0",
            "--monitoring-port=8080",
            "--graffiti=1-geth-prysm",
            "--wallet-dir=/validator-keys/prysm",
            "--wallet-password-file=/prysm-password/prysm-password.txt",
            "--beacon-rpc-provider=172.16.0.13:3500",
            "--beacon-rest-api-provider=172.16.0.13:3500",
            "--enable-beacon-rest-api"
        ],
```

```
            "--beacon-rpc-provider=172.16.0.13:3500",
            "--beacon-rest-api-provider=172.16.0.13:3500",
```

The Prysm VC tried to connect to the Prysm VC with the same port for the
beacon API and the gRPC.

Now, it is:

**VC**:
```
...
            "--beacon-rpc-provider=172.16.0.13:4000",
            "--beacon-rest-api-provider=http://172.16.0.13:3500"
...
```

BN:
```
...
 "--rpc-host=0.0.0.0",
            "--rpc-port=4000",
            "--http-host=0.0.0.0",
            "--http-cors-domain=*",
            "--http-port=3500",
...
```

---------
Signed-off-by: Barnabas Busa <barnabas.busa@ethereum.org>
Co-authored-by: Barnabas Busa <barnabas.busa@ethereum.org>