Our best guess is we ran naming styles on open files only for two
reasons:

1. At the time, we only supported .editorconfig in-proc, so
   out of proc wouldn't have used the right settings.
2. Even if we were running in-proc, there might have been performance
   issues since we were running across a lot of files.

Neither of these concerns apply at this point: we now support
.editorconfig out of proc (both in the legacy path and the new path) and
since we're already running other analyzers that use .editorconfig,
the cost of processing it will exist regardless.

Remove some test input to reduce execution time

Fix export provider factory caching

Speed up TempPECompiler

This API has always accepted null as a shortcut for an empty array, so
this annotates it accordingly.

Properly generate suppression attributes (including usings/imports)

Properly exclude changes to unchangeable documents from being applied

Co-Authored-By: NManish Vasani <mavasani@microsoft.com>

Co-Authored-By: NManish Vasani <mavasani@microsoft.com>

Co-Authored-By: NManish Vasani <mavasani@microsoft.com>

Co-Authored-By: NManish Vasani <mavasani@microsoft.com>

Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1057089

Code block callbacks

Enable nullable reference types for Microsoft.Build.Tasks.CodeAnalysis

Optimize compilation tracker for solution close

Remove dependency on TPA list for testing

Fixes #40629

Update code style analyzer to 3.5.0-beta3-20078-04

Update Code Style links.

Check cancellation in GeneratedCodeTokenWalker