Debug adapter type traceability

[roblourens]

I saw a couple SO questions where a user mentioned errors they saw while debugging, but could not say which extension was responsible for the debugging. Someone should be able to figure it out, but I noticed that there isn't really good traceability from launch config to extension and vice versa. And you could have 5 extensions installed for X, with two different debuggers, and it's not obvious which you're using to debug. Example:

Here's my launch config, which extension am I using? Maybe hovering over the value here could show the extension display name.

(Also opened #14681 to track this)-> Which debug types are supported? I have to read the readme (I'm not sure someone in this situation would look at this page, but it might be good to have the debug adapter "type" here).

[octref]

cmd-click -> goes to extension page might also be a good addition.

[vscodebot]

This iteration we focus on issue grooming. This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!