Update the project.lock.json for FakeSign and upload a new nuget zip

#load directives...

It isn't needed, as the Workspace will notice changes in the Compilation
due to #loads.

Tidy up nuget artifacts for ResultProviders...

Fixes a subtle bug in branch optimizer.

Making stack scheduling optimizations more robust and fixing #4828

Performance improvements for the v2 analyzer driver

Using correct case in-sensitive comparer
Fixes #4782

Address PR feedback

Remove check for 'IgnoreCase In CSharpAddImportCodeFixProvider we
explicitly override IgnoreCase to be false.  Therefore, we will never use
a case in-sesitive comparer.

Prioritize uncommenting single line comments over multi-line comments.

Fixes: #548

1) Reduce number allocations in the analyzer driver that show up perf traces for Picasso.
2) Currently we maintain a cache of CompilationWithAnalyzers for projects being actively analyzed. This is causing the VM to rise and also forcing GC to kick in at different phases causing regressions at various scenarios. The fix is to just create a new CompilationCompilationWithAnalyzers instance for each document/project analysis request.

Add support for multi-dimensional arrays of rank 1 to C# compiler.

Fixes #4924.

Start outlining span after all the whitespace on the target token.

list exceptions from the doc comments when showing quick info

"branch over branch" optimization eliminates chains of trivial basic blocks from the graph, which is correct as long as trivial blocks are not reachable individually from outside via branches.
The "same as next" optimization can make a block trivial and if it was targeted by a branch, break the assumption, leading to a rare situation of some branches having stale offsets.

The fix makes sure if a block becomes trivial, its labels are moved to the next nontrivial block.

Fixes #4838
Fixes #4839

Fix Visual Basic Workflow v1 projects when events are hooked up

Update comment from b60a2b93

Fix inserting using inside namespace
Fixes #3080

speculative semantic model determine if we should use the fully qualified
name or not. What this approach failed to account for was if the name
was going to be simplified further due to the containing namespace. To
Fix this we run the simplifier over our document and check if there are
any changes made to the namespace. If this is the case, then we re-sort
the usings according to the simplified name.

Generate inaccessible getters and setters
Fixes #2407

NuGet restore output is blowing up our log files, so this should output only errors.

Fix project file for EE

https://github.com/dotnet/roslyn/pull/4965