This takes care of Microsoft.VisualStudio.Imaging and
Microsoft.VisualStudio.ImageCatalog, which for now aren't available
outside Visual Studio. ImageCatalog is a pretty simple data API so
one day it might be useful, but for now isn't.

Fixes dotnet/roslyn#23189.

* added time tracking to completion set.

from the point we start completion set to first time we are called from VS for best match (which indicate that completion set is actually shown to users first time for this particular completion session)

the event is vs/ide/vbcs/intellisense/completion

if completion is done without showing UI to users (etc or tab), then event will be marked as cancelled.

* added perf tracking to LB fix all.

there were already existing events so I just made those to include perf info (duration) as well.

among all those events, these 2 are ones we were planning to add

vs/ide/vbcs/codefixes/fixalloccurrencescomputation
this shows time from the point user invoked fix all to where we shows preview window to users.

vs/ide/vbcs/codefixes/applychanges
this shows time from user clicked Apply from preview window to where we actually applied the changes to VS

there are more events between them in case we want to dig in details later such as how long it took to calculate diagnostics, how many files are affected and etc.

also all related events have correlation id to group related code fix events. also for fix all case, it contains scope to show whether fix all is for document, project, solution.

* PR feedback. removed unnecessary parameter

* removed repeated correction id set

* updated comments.

Make the default suggested action behavior to not show a preview.  Only override that for fixes/refactoring.

* 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.

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 is necessary so that the light-bulb will dismiss with long running
suggested actions.  Otherwise, it will stick on the screen for the duration
of 'Invoke()'.

Note: integration tests already do a 'wait' after invoking to make sure
the light bulbs have finished.  So they are unaffected by this.