[Fix] Terminal startup failures can leave commands unresolved

[zoomote]

​Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

• Expanded the type-aware @typescript-eslint/no-floating-promises ratchet to integrations/**/*.ts and resolved all eight existing findings.
• Routed VS Code and Execa terminal startup rejections through the existing process error event so returned command promises reject instead of hanging.
• Added a caught async boundary for debounced workspace resets, awaited workspace reinitialization, and kept routine webview updates non-blocking.
• Added focused terminal and workspace failure-path coverage, while preserving OS-specific terminal test synchronization.

Why this change was made

Terminal process starts returned promises that were not observed, so an unexpected startup rejection could bypass the command promise's existing error channel. Workspace resets also launched reinitialization from a timer without handling rejection.

Impact

Terminal startup failures now reach callers deterministically, workspace reset failures are logged without becoming unhandled rejections, and future floating promises in integrations/** fail lint. Successful execution timing remains unchanged.

[codecov]

Codecov Report

❌ Patch coverage is 90.90909% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/integrations/workspace/WorkspaceTracker.ts	88.88%	0 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!