* Write Roslyn assembly version to DependentAssemblyVersions file

* Depend on GetAssemblyVersion to ensure AssemblyVersion has been calculated

* Update implicity declared type expression nullability:
- When updating the implicit type in a declaration also update the bound type declaration nullability
- Record nullability for inferred foreach variable
- Add nullable public api tests
- Add nullable tests

Implement generate method and constructor with top-level nullability tracking wrapper

* mark NFW from OOP critical

currently, whenever OOP throws an exception, we show infobar saying "restart VS". whenever that happens, we report NFW. now those NFW will be marked as critical and we will stop reporting NFW after that in VS.

basically making critical NFW behavior same as fatal watson in VS. and management will treat critical NFW same as fatal watson.

also, now we will show callstack like code fix exception when info bar is shown

* xml document fix

* fix build break.

* changed button to hyper-link to follow same pattern as other info bar (code fix)

show remote exception in callstack view.

* introduced enum for Watson Severity

DisposableWaitAsync often completes synchronously

Pass CancellationToken instead of CancellationTokenSource

Avoid captures in SqlConnection.ReadBlob

Update AnalyzerRunner to support IIncrementalAnalyzer testing

* Learn from comparisons to non-constant, non-null values

* Update comment

* Remove unused local function

* Remove another unused local function

* Check for null constant before trying to learn from notNull == maybeNull. Add tests

* More tests, more cleanup

* Add conditional access with || test

* More test updates from feedback

* Cleanup

* Change some locals in tests to parameters

Update FindImplementationsForInterfaceMemberAsync to correctly handle ambiguous type returns (#35853)

FindImplementationsForInterfaceMemberAsync checks for forwarded types using SymbolFinder.OriginalSymbolsMatch, which expects non-null compilation for both the project containing the interface and the project containing the symbol to compare to. Until now, most instances have found equivalence without falling through, but in cases where the type forwarding isn't completely verified a non-null compilation for the interface symbol is needed as well. See VerifyForwardedTypes for the logic being used.

In #35786 the type System.Text.Encoding is provided by a a NuGet reference and could be ambiguous based on the build target. The OOP service attempts to find the correct type resolution but needs the original symbol compilation to verify.

Without this fix, FindAllReferences may cause a null deref and fail.

Fixes #35786

* Update ILAsm and ILDasm version to match expected SDK version

* Fixed version numbers

This makes the extension method work again. The workaround is tracked by
https://github.com/dotnet/roslyn/issues/36093.

This catches places we're calling Construct() or
ClassifyConversion().

This enables basic support for applying top-level nullability to
parameters and the return types when generating methods.

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

Currently, the APIs for nullable reference types take a model that
instead of the top level nullability of a named type being on the
INamedTypeSymbol, it's carried along as a separate piece of information.
This causes a lot of churn for code that is used to passing along
ITypeSymbols today; one way to ease this is simply create a set of
wrapper types which carry it along for us but still implement
ITypeSymbol.

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

This change produced a 806MB (11.3%) allocation reduction in the scenario
described by #36114.