Leaner launch.json generation

[isidorn]

• Node Simplify generated launch.json vscode-node-debug#185
• C# Simplify generated launch.json  dotnet/vscode-csharp#2673
• Python Simplify generated launch.json vscode-python#3321
• Java Simplify generated launch.json vscode-java-debug#476
• C++ Simplify generated launch.json  vscode-cpptools#2819
• Chrome https://github.com/Microsoft/vscode-chrome-debug/issues/751
• Help Wanted Php Simplify generated launch.json  xdebug/vscode-php-debug#318
• Go Simplify generated launch.json  vscode-go#2120
• Powershell Simplify generated launch.json  PowerShell/vscode-powershell#1611
• React Native Simplify generated launch.json  vscode-react-native#830
• Help Wanted Ruby Simplify generated launch.json rubyide/vscode-ruby#404 thanks @YisraelV
• Docker Simplify generated launch.json vscode-docker#612

These are all the extensions from our top 100 which support debugging.

[isidorn]

@weinand houghts if node should be simplified, currently it generates the following file

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Launch Program",
            "program": "${file}"
        }
    ]
}

imho I like this and would not add any wizard that asks if you would like to launch / attach
I think the bigger issues are other extensions and I would start there

[isidorn]

@roblourens chrome currently generates this

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "chrome",
            "request": "launch",
            "name": "Launch Chrome against localhost",
            "url": "http://localhost:8080",
            "webRoot": "${workspaceFolder}"
        },
    ]
}

I also like that and I think we should be aligned with what node is doing.
What you profit from using quick pick to ask some questions? Did you notice that users get puzzled by something or that somethins is especially hard to setup? Like source maps for example?

[roblourens]

Configuring sourceMapPathOverrides and pathMapping is still an issue, but it's something you have to "discover" by looking at the app during runtime, I wouldn't try to make it easier during launch config creation.

If we want to optimize for few parameters by default, webRoot could be removed and defaulted to workspaceFolder. I think it helps to have it in the default config so it can be discovered more easily but I don't know how often it has to be changed.