Feature Request: Add Helix as a first-class relay option in ethereum-package

[Walentalien]

Summary

Please add Helix as a relay backend option to ethpandaops/ethereum-package, alongside the existing Flashbots integration. The goal is to enable testnet/sandbox deployments of Helix within Kurtosis using the familiar mev_type switch and package inputs so users can spin up validators + EL/CL clients + Helix relay in one command.

This would let client teams, researchers, and operators evaluate Helix in realistic topologies (single- and multi-node), benchmark latency, and explore PBS workflows end-to-end.

Why this matters (Motivation & Value)

1. Having Helix available under the same UX lowers friction and encourages testing.
2. Adding Helix makes it easier to compare relay behaviors, simulate failover, and test builder/validator flows with consistent infra.

Proposed user experience

kurtosis run github.com/ethpandaops/ethereum-package \
  --enclave helix-demo \
  '{"mev_type":"helix","network_params":{"preset":"minimal"}}'

mev_type accepts a new value: "helix".

Package spins up the Helix relay service(s) connected to the existing EL/CL stack.

Optional flags to toggle a Helix web UI / metrics, and a small simulator (optional).

Extend mev_type enum: ["none","flashbots","helix"].

[barnabasbusa]

@bharath-123 would you be interested in picking this up?

[bharath-123]

Yes I can pick this up.

[kckeiks]

+1 yeah, this would be great!