fix: reliable Stop, snappier console, consistent naming

[karan5028ji]

What & why

Two user-reported issues plus housekeeping:

1. Stop button "does nothing" / app stuck in Running
   supervise_run could block forever on thread.join() when a grandchild
   (winget's msiexec installer, DISM, etc.) inherited the stdout pipe and
   outlived the parent. optimizer:done never fired, so the UI stayed stuck
   in "Running" and Stop became a no-op.

   • Every run now lives in a kill-on-close Windows Job Object; Stop closes
     the job, killing the whole tree including escaped installers.
   • supervise_run never blocks on reader join — it always emits done after
     the drain grace.
   • Job is detached on natural completion so Start-Process panels/Explorer
     restarts survive the run.
   • taskkill /T /F kept as fallback when job creation/assignment fails.

2. App feels too slow
   Console re-rendered up to 4000 joined log lines on every ~80ms flush.

   • Console now renders only the last 300 lines.

3. Consistency: all remaining "PC Optimizer"/pc-optimizer references
   renamed to Win-Optimizer-Pro (title, package-lock, headers, restore-point
   description, debug env var).

Plus earlier fixes folded in: context-menu toggle reads real state, cached
listings can't hang (drain grace), locked temp folders are swept instead of
"already empty", Win11 ISO edition error handling, portable zip bundle target,
SSH flag for profile export.

Verification

• All three PowerShell modules parse clean (Parser::ParseFile).
• backend.js passes node --check.
• Not verified on this machine: cargo check and npm run build could not
  run (no Rust toolchain / no node_modules). The job-object code follows
  windows-sys 0.59 signatures; please build before merging.