isolate per-chain failures in getAddressType and catchUp

Two related resilience fixes for when one chain backend (typically lq via
the cs tunnel) is down or unreachable:

- getAddressType: when lq.getAddressInfo throws on a connection error
  (ECONNREFUSED / ETIMEDOUT / "Unable to connect"), fail with
  "liquid temporarily unavailable" instead of the misleading
  "unrecognized address". Users get an actionable message and we can
  tell user error from infrastructure problems in the logs.

- catchUp: wrap the per-chain listTransactions call in its own try/catch
  so a downed lq doesn't stop the bitcoin deposit-recovery loop (and
  vice versa). Logged via warnThrottled so a multi-hour outage doesn't
  spam the same error every tick.

Also drops a redundant /confirm double-call comment from catchUp — with
walletnotify reliable again, a single call is sufficient and avoids
piling on the /confirm race the new atomic lock is preventing.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

0 files changed, 0 insertions, 0 deletions