feat(daemon): using the exp backoff util on metadataDiff

[andreabadesso]

Motivation

Production incident on 2026-01-18: the daemon crashed with ETIMEDOUT in metadataDiff and required manual restart. The function had no retry logic, so a single transient DB connection timeout could have caused a fatal error.

Acceptance Criteria

• metadataDiff retries on connection errors (ETIMEDOUT, ECONNREFUSED, ECONNRESET, PROTOCOL_CONNECTION_LOST)
• Up to 5 retries with exponential backoff (1s → 2s → 4s → 8s → 10s max)
• Non-retryable errors fail immediately (no unnecessary delays)
• Error logging includes transaction hash for debugging

Checklist

• If you are requesting a merge into master, confirm this code is production-ready and can be included in future releases as soon as it gets merged
• Make sure either the unit tests and/or the QA tests are capable of testing the new features
• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.