Add "Install Debug Extension(s)" Action

[bamurtaugh]

The error message that appears when an extension is missing that contributes a certain debug type may be confusing or unclear to newer users (i.e. Configured debug type coreclr is not supported. may not make it evident that the C# extension is missing in .NET development).

I've added an Install Debug Extension(s) button that opens the Extensions view and filters by tag:debuggers @sort:installs:

A couple of outstanding questions:

• What precise wording would we like for the button? What would make the most sense for users? When I ran into this error, if I saw a button that indicated I could go install extensions to fix it, I would've been interested and inclined to click it.
• Should this button come before or after the button to Open launch.json?
• If you see any implementation improvements, I'd be happy to iterate on the code as this is my first time contributing to the core VS Code repo.

This PR fixes #103719

[isidorn]

@bamurtaugh thanks a lot for creating this PR and congrats on your first contribution to VS Code core 🎉
I like the work and here's some answers to your questions:

• I would call the button "Install coreclr Extension". And it would still do the same thing. Definetely no (s) since we do not do that in our UI. I was also thinking that we could filter the debug extensions in the extension view by 'coreclr' keyword but unfortunetly this does not find the C# extension.
• Open Launch.json should be the first action and the one selected by default, since I think that is the most likely action a user takes. Though this order also works for me
• for the implementation improvements I will comment directly in the code

Thanks!

[isidorn]

Let me know when this is ready for review - no hurries.
Until then assigning to On-Deck.

[bamurtaugh]

@isidorn Sounds great, thank you! Hoping to get some time to work on it more this week.

[bamurtaugh]

@isidorn Thank you again for all of the help and feedback! I worked to incorporate your suggestions. Please feel free to review again whenever you get a chance and let me know what you think.

[isidorn]

The Action looks good!

[bamurtaugh]

Thank you!

[isidorn]

This way you are creating a new instance of the commandsService, which we do not want. We use dependency injetion across our codebase so that different objects can get ahold of services.
So you shuold just change the debug service consuctor arguments to take an additional argument, something like
@ICommandService private readonly commandService: ICommandService

The @ is a special vscode annotation which means inject me with that service.

[bamurtaugh]

Thanks for the insights here- I added @ICommandService private readonly commandService: ICommandService as an argument to the constructor. Let me know what you think.

[isidorn]

@bamurtaugh nice work. I have reviewed again and there is just one more thing which I commented in the code.

[bamurtaugh]

@isidorn Thank you for reviewing again! I made some adjustments based on the last comment.

[isidorn]

Looks good, merging in. Thanks for this PR 👏 ☀️

[bamurtaugh]

Thank you for all your help, @isidorn! This has been a great learning experience, and it's really neat to have it merged in 😄