SSH: Audit error handling

[joshspicer]

In cases where an unsupported scenario is detected, capture with #10248 and emit an actionable error case

There are several angles to this that we can take.

• Capture the error in the first place (fundamental here)
• Emit a human-readable version of the captured error.
• Tie into error reporting for easier time opening issues (or pass to an LLM, etc... as a stretch).

Examples of places where we can improve error surfacing

• Detect the error case where scp cannot copy to remote because remote doesn't have scp installed #10200
• When installing VSCode Server on a ssh remote, verify the scp transfer status and display appropriate error if transfer failed #10201
• Can't connect to non-admin Windows account (Get-CimInstance PermissionDenied) #2648 (comment)
• [Remote-SSH Bug]: Unable to use remote ssh, error log: Resolver error: Error: Creating 'sh' subshell timed out #10325
• Server Install path issue: [Remote-SSH Bug]: Hangs after "Copy server to host" #10345
• Proxy 407 status code when proxying http requests: [Remote-SSH Bug]: Remote SSH connect fails on box w/o internet connection #10344
• macOS Sequoia detect error about "Local Network" settings #10441
• (maybe) [Remote-SSH Bug]: Reconnect to vsode fails with install script error #10453
• Improve architecture unsupported message to have link to docs with information on device examples #3468

[joshspicer]

The pre-release now has as setting remote.SSH.experimental.enhancedSessionLogs that will surface the new collection of errors/warnings that is happening behind the scens. Additionally, it will present known errors in a more user-friendly way. As changes are made to the extension, this surfacing will continue to improve