perf(net): hold wallet scans at connect, in the background and on tab entry

- Connect gate: after the node starts answering, wallet scans wait until the
  lock state is known and the node knows its tip (or the wallet has fewer
  than 500 transactions), at most 20 s. A node already behind latches the
  sync profile from the connect's getinfo. Meanwhile a list-only pass keeps
  the address list and the cached history up, and the session's first
  balance and per-address balances are read once even while catching up,
  so the wallet shows its last-synced values instead of 0.
- Background: minimized, hidden, or covered without focus (3 s debounce,
  any input cancels) polls only the chain state every 15 s. Wallet scans,
  the mining poll, price, nudges and auto-lock interaction tracking pause;
  auto-lock now fires while minimized. Leaving a held profile marks every
  timer due again.
- Tab entry marks the timers due instead of forcing scans; a stale list or
  a never-loaded history still loads on entry.
- The scan entry points own the hard gates, failed enumerations keep the
  previous lists behind a retry hold, and failed balance calls never
  overwrite known balances with 0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/services/refresh_scheduler.h

@@ -43,8 +43,17 @@ public:
     // the lightweight Console tab syncs faster than the Peers tab. Reverts to the per-tab profile
     // once sync completes. (Tx/address/balance data is incomplete mid-sync anyway.)
     static constexpr Intervals kSyncProfile{10.0f, 0.0f, 0.0f, 0.0f};
+    // While the window is in the background (minimized, hidden, or covered without focus): only the chain
+    // state, slower. It keeps sync detection, the lost-connection check and the balance's own rare poll
+    // (auto-shield) alive; the wallet scans and peers wait for the window to come back.
+    static constexpr Intervals kBackgroundProfile{15.0f, 0.0f, 0.0f, 0.0f};
+    // How long the sync profile holds after the node last read "behind" (see the Core callback). Must
+    // outlast two Core polls in every held profile, or it could lapse between two "behind" readings.
+    static constexpr float kSyncSettleSeconds = 30.0f;
 
     static Intervals intervalsForPage(ui::NavPage page);
+    // The profile in force: background, else syncing, else the page's.
+    static Intervals selectIntervals(ui::NavPage page, bool syncing, bool background);
 
     void applyPage(ui::NavPage page);
     void setIntervals(Intervals intervals);