Add CI workflows for release and execution client sync tests

[pablomendezroyo]

Introduce new CI workflows for managing releases and executing client sync tests. The workflows allow for manual triggering and automate the build, test, and release processes for various execution clients. This enhances the testing and deployment pipeline.

[github-actions]

✅ SYNC TEST REPORT - PASSED

This CI runs on a real DAppNode using the same RPC calls a user would make to configure a staker setup: execution client, consensus client, web3signer, MEV-boost, and relays. The self-hosted runner is pre-loaded with synced (or near-synced) execution client volumes, enabling fast sync and attestation tests with any client combination. Consensus clients use checkpoint sync, so no pre-synced volume is required.

Sync Test: Verifies that both execution and consensus clients reach a synced state. This test ensures the staker configuration is valid and clients can synchronize with the network.

📦 Clients Used

Component	DNP Name	DNP Version
Execution	hoodi-erigon.dnp.dappnode.eth	0.1.1
Consensus	prysm-hoodi.dnp.dappnode.eth	0.1.5
Web3Signer	web3signer-hoodi.dnp.dappnode.eth	0.1.3
MEV Boost	mev-boost-hoodi.dnp.dappnode.eth	0.1.1
Network	hoodi

🔖 Version Tracking

Execution Client Versions

Stage	Version
Before Install	erigon/3.2.0/linux-amd64/go1.24.7
After Install	erigon/3.2.0/linux-amd64/go1.24.7

Consensus Client Versions

Stage	Version
Before Install	Prysm/v7.0.1 (linux amd64)
After Install	Prysm/v7.1.2 (linux amd64)

⏱️ Timing Measurements

Environment Setup

Operation	Duration	Status
SetStakerConfig	51.452s	✅
PackageInstall	11.715s	✅

Test Execution

Operation	Duration	Status
WaitForBeaconchainSync	1m52.096s	✅
WaitForExecutionSync	8m54.301s	✅

Total Duration: 11m56s

🔴 Container Error Logs

⚠️ Showing up to 3 error lines per container. See CI logs for complete details.

DAppNodePackage-validator.prysm-hoodi.dnp.dappnode.eth:

2026-02-06T08:33:38.017182102Z time="2026-02-06 08:33:38.01" level=error msg="Failed to get health of node" error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 172.33.0.24:4000: connect: connection refused""
2026-02-06T08:44:06.574709298Z time="2026-02-06 08:44:06.57" level=error msg="Could not request attestation to sign at slot" error="rpc error: code = Unavailable desc = Could not get attestation data: the node is currently optimistic and cannot serve validators" prefix=client pubkey=0xb1a6afab47a6 slot=2346170

---

📋 View full CI logs