Fix: chainsync can break on old data

[JannikSt]

No description provided.

[Copilot]

Pull Request Overview

This PR addresses potential failures when syncing node data by adding robust error handling and refactoring inline error-prone code into a dedicated async function. Key changes include:

• Replacing unwrap calls with error handling via map_err.
• Introducing the async function sync_single_node to encapsulate node synchronization logic.
• Updating error types from Result<()> to Result<(), Error> for improved error propagation.

Comments suppressed due to low confidence (2)

discovery/src/chainsync/sync.rs:36

• [nitpick] The variable 'n' is ambiguous. Consider renaming it to a more descriptive name such as 'updated_node' for better code clarity.

let mut n = node.clone();

discovery/src/chainsync/sync.rs:40

• [nitpick] Consider using a structured logging framework instead of eprintln for error reporting to better support production diagnostics and log management.

eprintln!("Failed to parse provider address: {}", e);