Allow transient Windows GATT startup aborts to settle

[enaboapps]

Closes #673

What changed

• Waits up to two seconds for a successful Windows GATT startup abort to settle into Started.
• Fails immediately for aborts with a real Bluetooth error and for incomplete advertisement data.
• Keeps transient startup states as Initializing instead of recording a false runtime failure.
• Preserves recovery for non-started statuses after a provider is active.

Validation

• npm run lint
• npm test (74 frontend tests, 5 updater-feed tests)
• npm run build
• Main Rust formatting, Clippy with warnings denied, and tests (243 unit tests, 7 configuration tests)
• Startup launcher formatting, Clippy, and tests (2 tests)
• Updater verifier formatting, Clippy, and tests (2 tests)
• npm audit --audit-level=high (0 vulnerabilities)
• Pinned cargo-audit 0.22.2 against all three lockfiles (0 vulnerabilities; existing allowed warnings only)
• Rebuilt and verified the unsigned Windows UIAccess NSIS package
• On the affected Windows 11 PC, the patched native build reached advertising without the RC2 BluetoothError(0) failure or retry loop; RC1 was restored after the check