This milestone I am looking into simplifing generated launch.json for various extensions microsoft/vscode#62851

The launch.json that GO generates is attached at the end. This is cool and simple. However we can still do the following

• Go needs to activate on onDebugInitialConfigurations
• Consider to use quickPick in DebugConfigurationProvider to ask the user if he would like to launch file, launch package, connect to server, launch test package, launch test function and based on that create a launch configuration.
• Remove default fields which are not necessery like env, args. Both from the configurationSnippets and from the intial configurations
• What is the biggest pain point for go debugging setup, could we somehow help there with dynamicly providing debug configuratons or resolving them

{
    // 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": [
        {
            "name": "Launch",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${fileDirname}",
            "env": {},
            "args": []
        }
    ]
}