[Bug][VB] RudeEdit error message blindly blames AutoProperty

It fixes #3605

It fixes #3605

Remove dependency on Microsoft.CodeAnalysis.Workspaces

FixerWithFixAllAnalyzer references types in the Workspaces assembly in a
couple of places:
``` C#
private static string CodeFixProviderMetadataName = typeof(CodeFixProvider).FullName;
```

This creates a runtime dependency on Microsoft.CodeAnalysis.Workspaces.dll
which is part of VS but not part of the compilers (csc/vbc/vbcscompiler).
The analyzers that derive from this type thus work in VS but fail during
build with a `TypeInitializationException`.

The fix is to use hard-coded strings for the names of these types. As
they are part of the public API, their names won't be changing anytime
soon.

This does not remove the project-to-project reference to Workspaces.
Doing so would have required fixing up a bunch of `<see cref="..." />`
elements in the doc comments to use the full name of these types as well,
generally making them much uglier. This isn't necessary to fix the
runtime issue.

Fixes #3706.

FixerWithFixAllAnalyzer references types in the Workspaces assembly in a
couple of places:
``` C#
private static string CodeFixProviderMetadataName = typeof(CodeFixProvider).FullName;
```

This creates a runtime dependency on Microsoft.CodeAnalysis.Workspaces.dll
which is part of VS but not part of the compilers (csc/vbc/vbcscompiler).
The analyzers that derive from this type thus work in VS but fail during
build with a `TypeInitializationException`.

The fix is to use hard-coded strings for the names of these types. As
they are part of the public API, their names won't be changing anytime
soon.

This does not remove the project-to-project reference to Workspaces.
Doing so would have required fixing up a bunch of `<see cref="..." />`
elements in the doc comments to use the full name of these types as well,
generally making them much uglier. This isn't necessary to fix the
runtime issue.

Fix modified path to nuget.exe

RudeEdit error message has a placeholder not filled in

This fixes #3604 by passing the display name for rude edit diagnostics.

Fix typos

Remove reference to Cci.IModule from PEWriter

PEWriter refactoring: sync PE header structures with those of PEReader

More PE header tests

This fixes #3604 by passing the display name for rude edit diagnostics.

Include usings debug info for expr-bodied members

Avoid translating global imports in presence of declaration errors

Don't look for labels in UsingsBinders

They were getting dropped in ```MethodCompiler.BindMethodBody```.

Prefer statements to expressions in the Immediate Window

...as in the native expression evaluators.

Note: VB is unaffected since it only allows implicit local declarations in
the Immediate window.

CR: @KevinH-MS, @cston

Fixes #3822

Add PE header test

We were asserting because the lookup was nonsensical.

Fixes #3817

Report diagnostics when short-circuiting emit

As an optimization, submissions not containing declarations are not
emitted.  However, when we short-circuit emission, we also skip diagnostic
reporting (e.g. in usings) that can trigger an assert in the next
submission (which assumes that all errors have been reported).

Fixes #3795

[EnC] Update UnitTests to use resource strings

Fix #1853 and #2657

Fix #1853 and #2657

Reduce casts between uint and int in PE writer

Organize Interactive solution folder...

This change adds a couple sub folders (Features, Host, Repl, Setup) and moves BasicVisualStudioRepl back to Interactive.

Cleanup string writing methods on BinaryWriter

Revert "Make APIs related to scripting and interactive internal for RTM"

Fix Null Exception crash