[BUG] Header-sync start-up timeout blocks entire node for 10 min

[auricom]

Problem
On eden-mainnet, a full node trying to connect to the sequencer with p2p sync hangs for the full 10-minute timeout inside HeaderSyncService.Init() and is unusable during that period.

Non aggregator node logs :

INF headers not yet available from peers, waiting to initialize header sync
error="failed to fetch height 452756 from peers: header: not found"
component=HeaderSyncService retry_in=1000

The node is blocked even though other sub-services (e.g. DataSync) are ready to proceed.

Root-cause
The hard-coded 10-minute timeout in:

https://github.com/evstack/ev-node/blob/main/pkg/sync/sync_service.go#L356-L357

is applied synchronously during service start-up.
If no peer currently advertises that height, the whole service (and therefore the node) waits until the timeout expires before it marks itself as “initialized”.

Expected behaviour
Header-sync should never block node start-up.
If the header is missing, the service should:

• mark itself as “degraded” but running,
• keep retrying in the background,
• let dependent services decide whether they can already proceed.