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

Allow using a custom dora image and specifying custom env variables.
This is especially useful for early testnets that might need disabling
some features via ENV vars
(eg. `KILLSWITCH_DISABLE_SSZ_REQUESTS=true`,
`KILLSWITCH_DISABLE_SSZ_ENCODING=true`)

This PR adds a new config argument called `participants_matrix`, which
allows the user to easily spin up a matrix of EL/CL combos. The `el` and
`cl` keys within this argument can be fully fledged normal
`participants`, so they support the exact same arguments.

For example:

# Example 1
```
participants_matrix:
  el:
  - el_type: geth
  - el_type: besu
  - el_type: reth
  cl:
  - cl_type: nimbus
 ```
 
 
 This config would create the following participants:
 - `nimbus-geth`
 - `nimbus-besu`
 - `nimbus-reth`

# Example 2
```
participants_matrix:
  el:
  - el_type: geth
  - el_type: besu
  - el_type: reth
  cl:
  - cl_type: nimbus
participants:
 - el_type: nethermind
   cl_type: lighthouse
 ```
 This config would create the following participants:
 - `nimbus-geth`
 - `nimbus-besu`
 - `nimbus-reth`
 - `lighthouse-nethermind`
 
 
# Example 3
```
participants_matrix:
  el:
  - el_type: geth
  - el_type: besu
  - el_type: reth
  cl:
  - cl_type: nimbus
     count: 5
 ```
 This config would create the following participants:
 - `5x nimbus-geth`
 - `5x nimbus-besu`
 - `5x nimbus-reth`

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

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

The flag `--validators-builder-registration-default-enabled` must be
used when VC/BN are combined. Otherwise validators won't be registered.

At startup Besu does not return a good gas price estimation (WIP to fix
this) and the default number of accepted connection is not enough to
sustain the tx_spammer, so this PR tune some options to allow to use the
tx_spammer wth Besu.

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

* use `electra-support` image for assertoor when electra fork epoch is
set
* use `peerdas-support` image for assertoor when peer das fork epoch is
set
* use `latest` image for minimal preset (now naively supported)

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

Serves all network config files via apache under the `/network-configs/
path.

```
/network-configs/besu.json
/network-configs/boot/
/network-configs/boot_enr.txt
/network-configs/boot_enr.yaml
/network-configs/bootnode.txt
/network-configs/bootstrap_nodes.txt
/network-configs/chainspec.json
/network-configs/config.yaml
/network-configs/deploy_block.txt
/network-configs/deposit_contract.txt
/network-configs/deposit_contract_block.txt
/network-configs/deposit_contract_block_hash.txt
/network-configs/genesis.json
/network-configs/genesis.ssz
/network-configs/genesis_validators_root.txt
/network-configs/mnemonics.yaml
/network-configs/parsedBeaconState.json
/network-configs/tranches/
```

previously we were using github.ref which would be main for two
different PRs making the concurrency group in valid

head_ref should work for on pull request events and that should be the
source branch

Adds PeerDAS (EIP7594) support for dory by using a [custom
image](https://github.com/ethpandaops/dora/pull/61)

🤖 I have created a release *beep* *boop*
---


##
[3.0.0](https://github.com/kurtosis-tech/ethereum-package/compare/2.2.0...3.0.0)
(2024-05-06)


### ⚠ BREAKING CHANGES

* add mev-rs relay/builder/boost
([#586](https://github.com/kurtosis-tech/ethereum-package/issues/586))
* upcoming file path change in kurtosis upstream
([#582](https://github.com/kurtosis-tech/ethereum-package/issues/582))

### Features

* add apache file server
([#581](https://github.com/kurtosis-tech/ethereum-package/issues/581))
([205256a6](https://github.com/kurtosis-tech/ethereum-package/commit/205256a6d79303719973655b459e803d9b8e311f))
* add enr/enode to apache
([#589](https://github.com/kurtosis-tech/ethereum-package/issues/589))
([b789e170](https://github.com/kurtosis-tech/ethereum-package/commit/b789e1705f076ec6aa01ceffbf5fbeebb02d8c0f))
* add execution client urls to dora config
([#588](https://github.com/kurtosis-tech/ethereum-package/issues/588))
([2a20d5ad](https://github.com/kurtosis-tech/ethereum-package/commit/2a20d5ad7d2bf8f9a9eb2b619681b438810176d2))
* add mev-rs relay/builder/boost
([#586](https://github.com/kurtosis-tech/ethereum-package/issues/586))
([525a8fb3](https://github.com/kurtosis-tech/ethereum-package/commit/525a8fb3d794f8030a574f55f3a7e719c1b58dca))
* Add peerdas support
([#591](https://github.com/kurtosis-tech/ethereum-package/issues/591))
([14296cab](https://github.com/kurtosis-tech/ethereum-package/commit/14296cab11d8c7a9572cf57a37980e1d93285cad))
* add snooper urls to assertoor config
([#571](https://github.com/kurtosis-tech/ethereum-package/issues/571))
([87f383fb](https://github.com/kurtosis-tech/ethereum-package/commit/87f383fbc7f9e28d383853fcb7cd491abe13a0cc))
* allow setting exit ip address
([#584](https://github.com/kurtosis-tech/ethereum-package/issues/584))
([aabc942c](https://github.com/kurtosis-tech/ethereum-package/commit/aabc942c4e8534288f28cdbb1e9e55f2613f383c))


### Bug Fixes

* non-existent field access on error message
([#577](https://github.com/kurtosis-tech/ethereum-package/issues/577))
([8515d276](https://github.com/kurtosis-tech/ethereum-package/commit/8515d276056a47f9e6a77dd498f823042bff1a8f))
* participant redefining global flag
([#573](https://github.com/kurtosis-tech/ethereum-package/issues/573))
([9139f4b4](https://github.com/kurtosis-tech/ethereum-package/commit/9139f4b4c77bc43477740972512171d7f28bfa84))
* path for shadowforks post kt update
([#585](https://github.com/kurtosis-tech/ethereum-package/issues/585))
([e0622a77](https://github.com/kurtosis-tech/ethereum-package/commit/e0622a77305732e01ee0fce183fda15c3dcd2dad))
* remove erigon's --chain parameter
([#575](https://github.com/kurtosis-tech/ethereum-package/issues/575))
([02b9c504](https://github.com/kurtosis-tech/ethereum-package/commit/02b9c50495f9b8cce0b0df502f19b37c0cb21ffd))
* upcoming file path change in kurtosis upstream
([#582](https://github.com/kurtosis-tech/ethereum-package/issues/582))
([8d7c4f9c](https://github.com/kurtosis-tech/ethereum-package/commit/8d7c4f9c1feba07511c22d006b5121b45893f642))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

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

This PR introduces a new mev boost/mev relay created by @ralexstokes.
It can be triggered by:
`mev_type: mev-rs`

It gets rid of the previously used `full` flag and flashbots will work
under the `mev_type: flashbots` following this PR.

upcoming version of dora uses execution layer clients to crawl the
deposit contract log.
This PR adds the execution client urls to the dora config.

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

Fixes #576

Now it correctly results in the error message:

```
There was an error interpreting Starlark code 
Evaluation error: fail: Unsupported launcher 'foo', need one of 'lighthouse,lodestar,nimbus,prysm,teku,grandine'
        at [github.com/kurtosis-tech/ethereum-package/main.star:104:55]: run
        at [github.com/kurtosis-tech/ethereum-package/src/participant_network.star:166:34]: launch_participant_network
        at [github.com/kurtosis-tech/ethereum-package/src/cl/cl_launcher.star:106:17]: launch
        at [0:0]: fail

Error encountered running Starlark code.
```