Sign SCI and SRM with Windows 10S compatible certificate.

Handled exception from a COM call to `IOleUndoManager`

* Add tests, change the behavior of comparing paramters

* remove virutal

* Resolve commits, add tests for property

* Resolve nits, naming and comments

* Add comments, move method down, renaming

* Fix typo

* Change modifiers and move method down

* Move helper methods into state and change them to static

* change modifiers

* Add a check

Require JoinableTaskContext be provided in the MEF container for EditorFeatures

Add structure provider for string literals

Ensure we react to metadata reference adds and deletes too

Add check to AbstractEditorFactory to load new WinForms designer if necessary

* Use SHA256 by default in command line compilers (/checksumalgorithm switch)

* Update XLF

Fix symbol resolution by applying groups at a time

Fixes #31482

Bail out on error type in CSharpTypeStyleDiagnosticAnalyzer

Add bail out cases for unused members analyzer

Don't crash if we can't fetch the IVsOutputWindow

Make method body generation not rely on destination type

Use an alternate approach to detect bail out case: presence of deconstruction info with null deconstruct method. The prior approach of bailing out on null type or converted type broke existing behavior (tests) that handle null type value.

1. Usages as an argument to `nameof`: We have multiple reports of these being false positives in presence of reflection based usages and in variour test frameworks. Fixes #32488.
2. Presence of 'dynamic' in C# - Conservatively bail out in presence of any dynamic operations. Fixes #32522.

When the AbstractEditorFactory needs to load the WinForms designer, it must first check the
project's TFM. If the TFM is netcoreapp and is greater or equal to 3.0, it specifies a
different string to the IVSMDDesignerService.CreateDesignerLoader(...) to indicate that the
new WinForms designer should be instantiated.

Eventually, this code will move into the WinForms designer itself.

Add support for ??= to NullableWalker

We potentially run the creation of the output window pane during the
shutdown of Visual Studio. This can happen because we're using
InvokeBelowInputPriorityAsync, which queues the switch to the UI thread
using IThreadingContext.JoinableTaskFactory.SwitchToMainThreadAsync().
This resulting continuation can run during package shutdown when
services are no longer available.

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

FileChangeWatcher wasn't specifying all the file watcher flags it should
have been. Reuse the constant that already existed for FileChangeTracker
so we get the same behavior.

FileChangeTracker is eventually going to be retired, and so I'm moving
over the constant to the long-term home.