feat(ui): say "Node busy" instead of "Launching dragonxd"; honest quit copy

A node rebuilding note witnesses for an hour was shown as "Starting
DragonX node... Launching dragonxd", which invited closing it.

- Overlay, a new NodeBusy banner and the status bar now say what the node
  is doing (rebuilding witnesses / catching up on blocks / up but not
  answering), with the elapsed time and Phase-1 block progress. A rebuild
  during startup warm-up replaces the stale "-28 Activating best chain"
  text, and the overlay re-applies its text once a second instead of only
  on a connect attempt (30s apart while the node is busy).
- Quit prompt: elapsed time, "Keep node running & quit" is the default,
  "Stop anyway & quit" becomes "Stop node & wait" (it no longer kills).
- A reinstall skipped because the node is still running now notifies.
- Status bar: don't repeat the warm-up status on the right, and don't
  print "Connected" there in non-English locales.
- i18n: 31 new keys in all 8 languages; 10 dead force-quit/old-modal keys
  removed; CJK subset rebuilt for the new glyphs.
- Tests: chooseDaemonStatus, NodeBusy banner priority, and every new key
  present in all 8 JSONs with matching printf conversions.

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

src/ui/node_status_banner.h

@@ -32,6 +32,7 @@ enum class NodeBannerReason {
     DaemonCrashed,    // the embedded daemon crashed repeatedly and auto-restart stopped
     LiteOpenFailed,   // lite build: the wallet failed to open
     NoPeers,          // connected to the daemon but no peer-derived tip (0 peers) — stalled, stale
+    NodeBusy,         // the node is up but busy (rebuilding witnesses / catching up / not answering)
 };
 
 struct NodeBannerState {
@@ -64,6 +65,12 @@ struct NodeBannerInputs {
     bool daemon_running        = false;
     int  daemon_crash_count    = 0;
 
+    // The node is running but busy with something it can't be interrupted out of (a witness rebuild, the
+    // startup replay) or too busy to answer RPC. Wallet data may be stale; a reconnect would only add
+    // requests, so the banner offers no action. node_busy_detail is the live, translated description.
+    bool        node_busy = false;
+    std::string node_busy_detail;
+
     std::string connection_status;  // human-readable status line (already translated)
     std::string daemon_last_error;  // DaemonController::lastError() (may be empty)
     std::string lite_open_error;    // lite: last wallet-open failure reason
@@ -89,6 +96,18 @@ inline NodeBannerState evaluateNodeStatusBanner(const NodeBannerInputs& in) {
         return s;
     }
 
+    // Full node, busy. Before the startup-phase returns below: the overlay sets daemon_initializing while
+    // the node is busy too, and the banner must still say why the wallet isn't updating. No action: a
+    // "Reconnect" would only queue more requests behind the busy node.
+    if (in.node_busy) {
+        s.show     = true;
+        s.severity = NodeBannerSeverity::Warning;
+        s.reason   = NodeBannerReason::NodeBusy;
+        s.action   = NodeBannerAction::None;
+        s.detail   = in.node_busy_detail;
+        return s;
+    }
+
     // Full node. In an expected startup phase → the loading/warmup overlay owns the screen, so no
     // banner. An active connect attempt likewise shows progress, not an error — don't flicker a
     // banner over it. (These return even if `connected` has flipped early, matching prior behavior.)