Plumb PowerShell Feedback providers into editor experience of VS Code

[StevenBucher98]

Prerequisites

• [X] I have written a descriptive issue title.
• [X] I have searched all issues to ensure it has not already been reported.

Summary

With FeedbackProviders in experimental feature of PowerShell, we should consider in the future once they are stable to have a way to utilize the feedback from these providers in the editor experience of VSCode.

Although like PSSA rules, this could potentially add an extra level of suggestions and discoverability for PowerShell code in scripts.

Proposed Design

Exact implementation and design may be tbd based on design changes of Feedback Providers but could be interesting integration and assistance in the editor. One way could be adding the feedback provider text to intellisense, or having a side bar that has these assistive tips included.

[JustinGrote]

My two cents:

1. The PSES host should be set up to display the same way they do in the PS console by default. This is what people will expect.
2. Simultaneously, the feedback should be plumbed into the Shell integration by default.
3. Option settings should be added to hide/suppress either one of these, so people can opt to go shell-integration only if they don't like the noise.

Because FeedbackProviders today do not provide any kind of line or column information to reference a script, I don't know how we would wire up Quick Fix or the Problems UI effectively. In shell integration however if a feature is ever added to Feedback Providers to run a "Quick Fix" or "Rewrite" of the command, that could show up in shell integration as clickable.