Allow upgrading to a launch config from a terminal command

[deostroll]

For running a nodejs app, I would have set environment variables in my terminal session. Later I decide to debug it, but I have to open a separate JavaScript Debug Terminal and repeat the process of setting environment variables.

There should be a way to convert an existing, say, powershell terminal, to a JavaScript Debug Terminal, so that I don't have to repeat setting my env variables again.

[connor4312]

Hm, interesting idea. We use environment variables to hook up debugging to VS Code. The difficulty with changing them on the fly is that dumping commands to change environment variables for the terminal is both difficult and unsafe. This is why when changing variables (e.g. when you change auto attach modes) terminals require a relaunch to get them to apply.

One option we could take is provide a command that could be run in the terminal, like code-toggle-js-debug (maybe wordy...) added to the PATH for embedded terminals.

[connor4312]

I think the way I want to approach this scenario is to have a context menu action on shell commands that involve Node.js processes to "Save at launch configuration" (in this menu here, with shell integration on)

I think that accomplishing the goal of wanting to "upgrade" from a normal shell into a debug environment, and also makes setting up launch configs quite easy.

cc @Tyriar / @meganrogge

[Tyriar]

This is blocked on #151937 feature work

[Tyriar]

To elaborate on my comment above, I'm not a fan of adding a persistent "create launch.json" to the command decoration menu. Instead I think we should add it to the contextual menu as that's the purpose we're aiming to have for that (high quality suggestions).

[connor4312]

The generic path for this now is copilot-debug: https://code.visualstudio.com/updates/v1_96#_debugging-with-copilot