I've done some manual testing, but there are no unit tests.

Existing unit tests are pass, except for ParseXml.Bug674567.  The fix is
either to change the baseline or to merge
https://github.com/dotnet/roslyn/pull/3957.

Conflicts:
	src/Compilers/VisualBasic/Portable/Scanner/Scanner.vb
	src/Compilers/VisualBasic/Portable/Syntax/CompilationUnitSyntax.vb
	src/Compilers/VisualBasic/Test/Semantic/Compilation/CompilationAPITests.vb

Initial support for visual basic interactive

Suppress supports warnings

Do not allow any form of inline lambda to be ref/out

Fix broken link in Building, Debugging, and Testing on Windows.md

Revert test workaround for 64bit execution of TestAnalyzerLoading_Error

Fixes #7111
Fixes #7112

Improve text for CS1615

Add Microsoft.CodeAnalysis.* to the set of assemblies ignored by Anal…

Simplify remote analyzer loading unit tests by avoiding use of a remote assert. Also remove the x86 only condition on the test.

Add Microsoft.CodeAnalysis.* to the set of assemblies ignored by AnalyzerDependencyChecker for missing dependency resolution.

Fixes #7049

Add support for registering an analyzer for concurrent execution of its actions

Merge from stabilization to master

Explicitly remove code model elements from the CleanableWeakComHandleTable when they are deleted

Ensure that an EnvDTE.CodeParameter.Name returns the correct value for parameters defined in metadata

Ensure that a relevant diagnostics are hit when passing the /i flags.
Ensure that a xml namespace import can be passed to a command line runner.

Fix assert failure for FileThatCannotBeDecoded under default codepage 936

There are WinForms scenarios where code model elements can be deleted and re-added, for example,
when the modifiers of a control on the designer surface are changed the control will be deleted
and immediately re-added. We must be sure to delete the element's node key from the
CleanableWeakComHandleTable or else an exception will be thrown when the element is re-added with
the same node key.

Comments on the behaviour of the interactive mode.
Add unit test for the binder fix.
Add unit test for command line parsing.

Ensure that an EnvDTE.CodeParameter.Name returns the correct value for parameters defined in metadata

The issue is that the symbol display system will not return a name for a parameter unless
SymbolDisplayParameterOptions.IncludeName is set. This behavior seems like it might ultimately be
a bug in symbol display as that option is intended to control the display the parameters owned
by the targeted symbol, but probably shouldn't affect the display of the targeted symbol. However,
rather than updating symbol display (which would potentially have larger downstream impact), we'll
just include the option in this case.

Theme the rename dashboard's "New name:" TextBlock

Cache test results locally

Remove LTTNG warnings on Linux

change all [Fact] private tests to be public

Fix TypeChar handler in Interactive Window

Code Model: GetTypeSymbolFromFullName should not return unpredictable results when the type name was in an unsupported format

Do not run Add-Using on syntax errors.