* Merge pull request #12041 from heejaechang/buildsyncrace

found one more case where documentId can be null

* prevent VS from crashing if VS got shutdown while build error reporting is in progress.

* Update our NuGet package version to 1.3.2

* Update Microsoft.DiaSymReader.Native to 1.4.0 RTM (#12141)

* Enable building of release nuget packages.

This commit makes it so that we will always try to generate release nugets except if they depend on prerelease packages. If one of our nuget packages happens to depend on prerelease packages, then when building release nugets, we will simply print a message in the build output and skip release nuget generation for that package (and allow the overall build to succeed).

* Address code review feedback.

* Simplify script to use nuget.exe for prerelease dependency validation instead of adding custom logic in the script for this.

* Remove Microsoft.CodeAnalysis.EditorFeatures from list of prerelease nuget packages.

* Change the name of the error log file to skipped_packages.txt.

* fixed DifferenceViewer leak

this leak was responsible for about 14% of managed memory in customer's dump.

basically, in certain condition, if cancellation exception is thrown, we will not close difference viewer which cause
all text views to leak. that cause all taggers and text buffers to leak and that cause our preview workspaces to alive.
which in turn cause all solutions to alive and so on. all those objects (view, buffer, workspace, solution) are quite
big graphs. so ends up eat up 14% of memory.

added assert to make sure if we leak viewers again, we get some kind of notification.

* Display analyzer assemblies with no applicable diagnostic analyzers towards the end of analyzers list in solution explorer

For most cases, these are analyzer depedencies with no analyzers.
For few cases, these might be analyzer assemblies with no analyzers applicable for the given project langauge.
For few other cases these might be analyzer assemblies whose diagnostic analyzers could not be instantiated for some reason, and hence have no rules.

We still display such analyzers in the solution explorer so the user is aware that the project file contains these analyzer references, but display them towards the end to avoid clutter.

Fixes https://github.com/dotnet/roslyn/issues/12047

* Address PR feedback and completely hide the analyzer dependencies (analyzer assembly has no diagnostic analzyers and also has no load errors)

this leak was responsible for about 14% of managed memory in customer's dump.

basically, in certain condition, if cancellation exception is thrown, we will not close difference viewer which cause
all text views to leak. that cause all taggers and text buffers to leak and that cause our preview workspaces to alive.
which in turn cause all solutions to alive and so on. all those objects (view, buffer, workspace, solution) are quite
big graphs. so ends up eat up 14% of memory.

added assert to make sure if we leak viewers again, we get some kind of notification.

This reverts commit 1b6a83f9.

This reverts commit 7357c7ba.

loose up a bit on what happens when build error report on us errors on a file that doesn't exist in roslyn solution
but have error code we own.

we used to treat them as project level errors but that made us to sometime show one entry for multiple error reports.

now, we will at least show all of them, but things like double click will not work since we don't know which document it is.

Fixes https://github.com/dotnet/roslyn/issues/11464

Postpone AnalyzerChanged operations when analyzer is changed on file system to prevent deadlock #11019