[PortablePDB] Implement GetOffset, GetRanges, FindClosestLine

Remove test workaround for a fixed DiaSymReader bug 1068894

Produce an error when __makeref is used and TypedReference type is no…

Ensures that history always contains what user has typed

Remove SCC bindings

Canonicalize all interactive window commands

We no longer use SCC bindings in our project yet the definitions remained around and caused a dialog prompt on solution open.  Removing these as they are no longer needed

Initial work to add telemetry to Interactive Windows

- add telemetry for create/open/close Interactive Windows.

Refactor MetadataFileReferenceResolver classes

 1. Allow button names to have different casing than command names (which
should be PascalCase).
 2. Sidestep some name conflicts with other VS packages.

Switch Section honors NewLineForBracesInControlBlock option

Report a better exception when compiler test resource is not found

The cross platform legs are causing roughly ~10% of all our Jenkins jobs to fail
(3% Mac failure, 7% Linux failure).  The main source of the instability is the
NuGet and build step.  As a short term work around I'm adding retry logic to
those steps to get the false failure rate down.

Update the metadata reader to 1.1.0-alpha-00009

fixes #3539

Fix some analyzer load diagnostics IDs and a duplicate roslyn diagnostic ID

Fixes #3805 and #2990

Ensure that syntax tree actions are also re-executed by the solution crawler when compilation options (or analyzer rule severity) are changed.

Fixes #3796 

Fix mapping from line numbers to prompt spans

Fixes #3805 and #2990

Fixed the order of optimizing argument reordering temps and packaging…

Bonus: Tighten projection span list asserts.

Conflicts:
	src/Workspaces/Core/Desktop/Workspace/MSBuild/MSBuildWorkspace.cs

Ensure that syntax tree actions are also re-executed by the solution crawler when compilation options (or analyzer rule severities) are changed.

Fixes #3796

Modifications to bootstrap Roslyn on CoreClr without exceptions

Open source build improvements

Report diagnostics for exceptions within the analyzer driver.

We execute the analyzer driver's initialization and core analysis tasks on a background thread. Any exceptions from the driver itself (not the analyzer callbacks, we already report diagnostics for those) were getting swallowed and analyzer execution also skipped silently. See #2980 (comment) for an example.

We now report an exception diagnostic for analyzer driver crash (with the complete exception trace), so that the user knows what happened and we can diagnose the bug when the issue is reported.

Fixes #3005

We used to maintain a separate data structure (```PromptLineMapping```)
that kept track of the correspondence between line numbers in the surface
buffer and the indices of the corresonding prompt subject buffers.
Unfortunately, this data structure was being updated incorrectly,
resulting in multiple prompt entries for individual line numbers and
incorrect lookups because binary search was operating on an unsorted list.

A simpler approach is to associate a line number with each ```ReplSpan```
(a standin for a subject buffer).  We already have code for keeping this
list up to date and the entries are guaranteed to be ordered by line
number so we can still binary search for specific prompts.

A number of new asserts validate all modifications of the ```ReplSpan```
list to ensure that it behaves as expected.

This change solves a number of problems that were resulting in
problems compiling Roslyn with Roslyn on the CoreClr.
I believe these problems were being masked by catching
exceptions. The motivation for the changes is to be able
to run Roslyn building Roslyn on Clr using the LLILC jit.
LLILC cannot currently produce code to catch exceptions
so it is important to avoid needless throwing of exceptions.

1. CoreClr was raising FileNotFound exceptions when trying to load the
following assemblies:

```
System.Threading.Overlapped
System.Threading.ThreadPool
```

I added references to these in src/Compilers/CSharp/CscCore/project.json.

2. System.Runtime in the version previously referenced in project.son
had a reference to Internal.Uri. This is no longer the current module
(it has been replaced by System.Private.Uri). So I changed the
version number used in project.json from 22816 to 23109.

3. The path in these ruleset files:

  * src/Compilers/Core/CodeAnalysisRules.ruleset
  * src/Compilers/CSharp/CSharpCodeAnalysisRules.ruleset
  * src/Compilers/VisualBasic/BasicCodeAnalysisRules.ruleset

was "..\..\Tools\Microsoft.CodeAnalysis.Toolset.Open\Rulesets\Roslyn.ruleset"
which is not the current location of Roslyn.ruleset. It now is in
"..\..\..\build\Rulesets\Roslyn.ruleset". The incorrect path
was causing an exception to be thrown.

4. On the CoreClr csc uses a NoOpAnalyzerAssemblyLoader which just
returns null when asked to get the assembly. This was causing a
null reference exception. I added a null check to just return
in this case.

5. The VbcCore project.json was updated to match CscCore.

Don't skip executing analyzer compilation actions in the IDE when ClosedFileDiagnostics flag is turned off OR the analyzer reports only hidden diagnostics. Compilation actions and compilation end actions can report diagnostics on open files, so they must always be executed.

Fixes #4068