FDM v2.9.2

fix(2.9.2): tolerate slow rqbit first-spawn ("HTTP API did not come up")

- Widen the rqbit API startup wait from ~5s to ~30s. The first spawn right after
  an app update is slow because macOS Gatekeeper (and Windows Defender) re-scans
  the freshly-written rqbit binary; the short timeout surfaced a spurious
  "rqbit HTTP API did not come up" and blocked the torrent.
- Classify that error (and other rqbit/torrent-engine startup hiccups) as a
  transient network kind so it auto-retries with backoff instead of waiting on a
  manual Retry.

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