Diagnostics related feature requests and improvements

[mavasani]

This issue tracks all diagnostics/analyzers related feature requests and improvements in VSCode C# extension:

• [O# Parity] Dedupe build and live diagnostics #5728
• Add support for 'Current Document' option for background execution of analyzers #5949
• [SUGGESTION] Bring back Analyze Solution #6147
• Roslyn analyzers quickfix: Add option for Suppress / Suppressions #4595
• Support to allow configuring background analysis scope per-solution and/or per-project #5950
• [Feature Request] Disable analysis per project #4747
• [O# Parity] Nested code actions including FixAll support for code fixes and refactorings #5735
• Ruleset replacement in the vscode extensions #5727
• [BUG] Opening a solution with C# Dev Kit causes dotnet build to ignore .editorconfig analyzer settings #5885
• EditorConfig support flakey after LSP initialization / restart. #5874
• Roslyn analyzer CompilationEndAction action is never called in VS Code #5634
• Roslyn Analyzer works even though I disabled It #5998
• ArgumentException: Argument cannot be empty. (Parameter 'analyzers') #6057

[mavasani]

@arkalyanms @mikadumont - not sure if there is already a story tracking all diagnostics related work. If so, feel free to dupe this one and close it out.

[marcospgp]

Is there an issue for being able to load analyzers by linking to the .dll instead of installing them as a nuget package? This is required in order to use third party analyzers with Unity:

Unity doesn’t support the installation of Roslyn Analyzers or source generators through NuGet directly

https://docs.unity3d.com/Manual/roslyn-analyzers.html