* Update ILAsm and ILDasm version to match expected SDK version

* Fixed version numbers

Add initial support for 'notnull' generic type constraint.

See https://github.com/dotnet/csharplang/blob/master/meetings/2019/LDM-2019-05-15.md
Also fixes #36005.

* Add InteractiveHost as a NuGet package

* Make InteractiveWindow a package dependency

* Update InteractiveWindow version to 2.8.0

* Add missing package dependencies

Add EditorConfig feature flag

Generate assembly version without using the patch version.

Add initial checkpointing to the nullable walker.

Don't capture BoundNode when creating a LazyNoneOperation

Specify the version number in pieces so we can generate the assembly version using just the major and minor version numbers.

Don't read the same property twice in pattern matching when accessed through the same underlying object, but references of different types.
Fixes #34933

* Cleanup style

* Remove BlueSquiggleForBuildDiagnostic

* TableDataSource refactoring

* Remove DiagnosticData.Workspace

* Fix workspace reference

* Simplify GetTrackingPoints

* Simplify deduplication

* EqualsModuloLocation

* Simplify navigate to

* Specialize table item

* Fix assert

* Feedback

* Dedup TryNavigateTo

* Couple of renames

Merge release/dev16.2-preview2 to master

Don't offer 'convert if to conditional' if it crosses a preprocessor directive.

Add Default Interface Implementation tests for VB

Related to #35820, #35821, #35823, #35824, #35827, #35834, #35852, #35885, #35911, #35948.

Port DisposeAnalyzers to release/dev16.2-preview2

Upgrade Microsoft.CodeAnalysis.FlowAnalysis.Utilities PackageReference to latest version

Additionally, we do not mark the package reference to in Features.csproj as PrivateAsset as this leads to the assembly not getting included in the Features NuGet package and causes Omnisharp's analyzer execution to throw missing dependency assembly load errors.
Also update ExpectedDependency in DevDivInsertionFiles.csproj

Additionally, we do not mark the package reference to in Features.csproj as PrivateAsset as this leads to the assembly not getting included in the Features NuGet package and causes Omnisharp's analyzer execution to throw missing dependency assembly load errors.
Also update ExpectedDependency in DevDivInsertionFiles.csproj

Fix false positive inside catch clause (port of https://github.com/dotnet/roslyn-analyzers/pull/2501)

Address PR feedback: remove static cache, make FlowAnalysis utilities assembly load lazy and revert reference add to the FlowAnalysis assembly in Workspaces (only referenced in Features now).

(DisposableFieldsShouldBeDisposed)

We will now flag disposable creations in methods that do not escape the
method body (return value, out/ref params, assign to field/property, add
to collection, etc.). Additionally, we also flag disposable fields of
disposable types that are not disposed in the type's Dispose method.
Ported analyzers share the core dataflow analysis computation with the
analyzers in the roslyn-analyzers repo
(Microsoft.CodeAnalysis.FlowAnalysis.Utilities). This PR does not add
any code fixes. We already have a code
refactoring that offers wrapping a disposable creation within a using
statement. I am hoping to extend that to handle more cases and also
possibly convert it to a code fix in follow-up PR(s).

Fix import completion telemetry