[Chore] Enable Static analysis (FxCopAnalyzers) on C# Projects

[ryanbodrug-microsoft]

Summary of the new feature/enhancement

1. Enable Static analysis on each of the

`csproj files.  Project -> Properties -> CodeAnalysis -> Microsoft.CodeAnalysis.FxCopAnalyzers `

2. Set warnings as errors on each project
3. Fix any errors due to static analysis
4. Validate consistent behavior by testing locally.
5. Ensure unit tests pass.

Proposed technical implementation details (optional)

Fix the following projects:

• FancyZonesEditor.csproj <- blocked due to multi-mon improvements
• win-app-driver.csproj
• Telemetry.csproj <- [FxCop] Telemetry.csproj #6642, was reverted Farm swaps this file, will fail if we do this how everything currently is. The change honestly isn't really that massive

Done

• Wox.Infrastructure.csproj. - [fxcop] Wox.Infrastructure #7590
• Microsoft.PowerToys.Settings.UI.csproj - [fxcop] Settings UI #7559
• Wox.CrashReporter.csproj - [fxcop] Removed Wox.CrashReporter #7591
• Wox.Plugin.csproj - [fxcop] Fixes for Wox.Plugin (1of3) #7457, [fxcop] Fixes for Wox.Plugin (2of3) - Moved logger interface to Wox.Plugin #7464, [fxcop] Fixes for Wox.Plugin (3of3) - enable FxCop Analyzer #7465, [fxcop] Wox.Plugin devdocs update #7595
• Microsoft.Plugin.Uri.UnitTests.csproj - [fxcop] Microsoft.Plugin.Uri.UnitTests #7562
• Microsoft.PowerToys.Settings.UI.Runner.csproj - [fxcop] Settings UI runner #7485
• Microsoft.PowerToys.Settings.UI.Lib.csproj - [fxcop] Settings UI library (part 1) #7187, [fxcop] Settings UI library (part 2) #7257, [fxcop] Settings UI library (part 3) - exception handling #7385, [fxcop] Settings UI library (part 4) - project/namespace renames #7403
• Wox.Test.csproj - FxCopAnalyzer fixes for Wox.Test #7312
• Wox.Core.csproj - FxCopAnalyzer fixes for Wox.Core #7209, FxCopAnalyzer fix for Wox.Core (PR#2of3) - Removing unused JsonRPC files #7211, FxCopAnalyzer fix for Wox.Core (PR#3of3) #7212
• Microsoft.PowerToys.Settings.UI.UnitTests.csproj - [fxcop] Settings UI unit tests #6987
• ImageResizerUI.csproj - [fxcop] image resizer ui #6841
• UnitTest-PreviewHandlerCommon.csproj - [FxCop] Preview handler common #6833
• ColorPickerUI.csproj - FxCop with ColorPicker #6464
• ImageResizerUITest.csproj - FxCop on Image Resizer Tests #6481
• UnitTests-SvgThumbnailProvider.csproj
• UnitTests-SvgPreviewHandler.csproj
• PreviewHandlerCommon.csproj <- [fxcop] preview handler common #6762
• MarkdownPreviewHandler.csproj <- Fxcop markdown preview handler #6646
• ManagedCommon.csproj
• Microsoft.Interop.Tests.csproj <- [FxCop] Interop tests #6668
• SvgPreviewHandler.csproj <- [FxCop] Svg preview handler #6647
• UnitTests-MarkdownPreviewHandler.csproj <- [FxCop] Markdown preview pane unit tests #6758
• SvgThumbnailProvider.csproj <- FxCop and StyleCop for SVG thumbnail #6757
• PowerLauncher.csproj
• PowerLauncher.Telemetry.csproj. <- Adding fxcop to PowerLauncher.TelemetryProject #6259
• Microsoft.Plugin.Folder.csproj
• Microsoft.Plugin.Indexer.csproj
• Microsoft.Plugin.Program.csproj
• Microsoft.Plugin.Program.UnitTests.csproj
• Microsoft.Plugin.Shell.csproj
• Microsoft.Plugin.Calculator.csproj
• Microsoft.Plugin.Uri.csproj
• Microsoft.Plugin.WindowWalker.csproj <- Adding FxCop to Microsoft.Plugin.WindowWalker #6260

[ryanbodrug-microsoft]

@crutkas I've updated the title and description to include all csproj files that need static analysis. Because this is expanding the scope beyond the launcher plugins I will probably remove the InVEST milestone. What do you think?

[crutkas]

I'm good with that

[crutkas]

I'm going to close this out and create a new issue for a wrapper issue with StyleCop and FxCop. Few projects need to be touched