Merged it into the non-desktop specific project. Will make porting our
test projects to netcoreapp easier.

The portable test utilities project already multi-targets between
netstandard, netcoreapp and desktop. Having part of the desktop code
exist in a separate assembly makes it even harder to multitarget our
test projects. Combining them all together and fully embracing
multitargeting here.

This is in preparation of moving several other compiler test projects to
test against coreclr / mono.

fixed issue where same analyzer reference is installed in both vsix and nuget. deduplication in inproc analyzer manager wasn't present in OOP case. (#23772)

this doesn't address our workitem to merge those two. that work is a separate work item. this just follow what we currently do in proc.

Fix publish-assets.ps1 to call the right helper function

Ensure-DotnetExe should be Ensure-DotnetSdk.

Merge features/vs-for-mac-refactorings into master

Publish all relevant VSIX projects

Do not allow source suppression for VS/host diagnostics

Need to publish the individual VSIX projects which used to represent our
uber VSIX package. The LUT + project system still use these for their
integration tests.

Move to latest analyzer/compiler toolset packages and fix violations …

Fix semantic model on type parameters of local functions

This fixes the UI delay from force binding all assembly attributes during solution load.
Fixes #23775

Add mono test runner

Move to dotnet restore

LOC CHECKIN | dotnet/roslyn-master | 20171212

NormalizeWhitespace: no space between keyword and open paren, add newline before constraints (#23686)

Handle parentheses in explicit VB delegate creation scenarios.

One of the VB scripting tests changes the default culture to "de-DE" and
later prints out a string subject to localization. Now that we actually
have satellite assemblies with real translations where the runtime will
find them, we're getting the German version rather than the English
version.

The fix here is to simply update the baseline.

* made bucketting to be better even in telemetry site.

previous way made bucketting to be better in watson site but not telemetry site. this should make it to better on both site.

* turns out bucket number is 0 based for API but document is 1 based.

* changed to use hashcode rather than full callstack since watson will only use first 255 for bucketing.

Merge master into features/vs-for-mac-refactorings

* Fixes #11497 - Error on empty key path for signing

* Address PR Feedback

Standard updating of stuff for -beta3