ci: use GitHub App token for auto_check PRs to trigger downstream workflows

[3alpha]

PRs created by the default GITHUB_TOKEN don't trigger other workflows (by design). This switches to the TropiBot GitHub App token so that PRs opened by auto_check trigger sync-test.yml as expected.

[tropibot]

✅ 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-besu.dnp.dappnode.eth	0.1.4
Consensus	nimbus-hoodi.dnp.dappnode.eth	0.1.3
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	besu/v25.9.0/linux-x86_64/openjdk-java-21
After Install	besu/v26.4.0/linux-x86_64/openjdk-java-25

Consensus Client Versions

Stage	Version
Before Install	Nimbus/v25.9.2-9839f1-stateofus
After Install	Nimbus/v25.9.2-9839f1-stateofus

⏱️ Timing Measurements

Environment Setup

Operation	Duration	Status
SetStakerConfig	54.998s	✅
PackageInstall	32.449s	✅

Test Execution

Operation	Duration	Status
WaitForBeaconchainSync	0s	✅
WaitForExecutionSync	2ms	✅

Total Duration: 2m1s

---

📋 View full CI logs