Improvements to the developer inner loop experience for the extension.
Needs: PowerShell/PowerShellEditorServices#2202

Launch Config Pre-Launch Tasks

The regular, temp, and isolated launch configurations have been optimized two prelaunch tasks:

• A esbuild watch for vscode-powershell to detect code changes and rebuild the extension
• A invoke-build task for PSES that rebuilds the extension only if changes to the source have been detected since the last build.

Auto-Attach PSES Debugger

The launch configurations now auto-attach the PSES debugger rather than prompting for a PID.

Auto Extension Restart on Changes

When the extension is running in dev (debug) mode, changes to the extension files auto-trigger an extension host restart. In temp and isolated, this is pretty fast especially compared to a window reload.

PSES Hot Reload

Hot Reload is now enabled, allowing testing of in-flight changes. Really handy for Handler development.

Other Changes

• The .vscode folder configuration has been merged into the code-workspace file due to limitations in calling tasks from code-workspace launch configs. All devs should be using the code-workspace file anyways.
• Docs were updated to provide clarify on these changes
• The workspace file was renamed in order to be more clear this is specifically for the vscode-powershell extension.