Reduce allocations from the ConcurrentDictionaries in TypeSymbol interface implementation maps.

Address couple of issues related to analyzers: 

1) Don't crash command line builds when reporting analyzer diagnostics. Reporting analyzer diagnostics may involve invoking user code for LocalizableString message, which may throw while finding resources or for other unknown reasons. We catch exceptions from these callbacks and report a diagnostic with the inner exception message.
 I verified that this fixes the crash seen in #271 and #813 and we started seeing this new info diagnostic.

2) Workaround for #271: The underlying cause of the crash is that our assembly resolver/CLR is unable to fallback to the main assembly for resources and ends up looking for the satellite resource assembly. We had seen this crash quite a while back, but it went away and this seems to have come up again. Workaround, as applied back then, is to mark the analyzer assembly with NeutralResourcesLanguageAttribute.
 I verified that adding this attribute to our core analyzer assemblies caused the resource to be correctly found and we don't even see the exception diagnostic from (1) above, but instead the actual diagnostic reported by the analyzer.

Disable tests related to GitHub issue #204

Fix #565: Syntax node actions are not called for field declarations in compiler analyzer driver if the declaration defines multiple variables

Simplify logic for execution of syntax node actions for field declarations: If there are multiple decls, execute syntax node actions for entire field decl (and its descendants) when processing symbol declared event for first field within it, and skip syntax node actions for rest of fields defined within that declaration.
 Current logic is unnecessarily complex in that it tries to execute syntax node actions for individual variable declarators when processing corresponding field symbol declared event, and executes the node actions for shared nodes (e.g. defining type syntax node) when processing first field symbol, and caused this bug to sneak through.

Added regression tests for compiler driver (VB and C#) and IDE driver.

Fix #671 to handle broken code case where there are multiple overrides of DiagnosticAnalyzer.SupportedDiagnostics property

1) Don't crash command line builds when reporting analyzer diagnostics. Reporting analyzer diagnostics may involve invoking user code for LocalizableString message, which may throw while finding resources or for other unknown reasons. We catch exceptions from these callbacks and report a diagnostic with the inner exception message.
I verified that this addressed the crash seen in #271 and #813 and we started seeing this new info diagnostic.

2) Workaround for #271: The underlying cause of the crash is that our assembly resolver/CLR is unable to fallback to the main assembly for resources and ends up looking for the satellite resource assembly. We had seen this crash quite a while back, but it went away and this seems to have come up again. Workaround, as applied back then, is to mark the analyzer assembly with NeutralResourcesLanguageAttribute.
I verified that adding this attribute to our core analyzer assemblies caused the resource to be correctly found and we don't even see the exception diagnostic from (1) above, but instead the actual diagnostic reported by the analyzer.

Refactor ResultProvider (incorporating Concord API changes)...

1.  DkmClrValue.InspectionContext has been removed, so a separate instance needs to be passed to all the methods that need it.
2.  DkmClrValue.EvaluateDebuggerDisplayString is now async.  In order to avoid complicated plumbing of completion routines through result expansion, I've moved the creation of DkmEvaluationResults from *Expansion to the ResultProvider.  Expansion now produces EvalResultDataItems that contain all the information necessary to produce DkmEvaluatoinResults in a single place, just before returning from the ResultProvider entry points.  New async plumbing/Exception handling is localized to the entry points.
3.  There are several places that the API now allows passing format specifiers.  We do not intend to support those scenarios in C#/VB, so we will ignore them.

Use TryGetValue followed by TryAdd to avoid delegate allocation.

Make OutliningSpan Creation not assume MultiLine Comment always end with...

Make VB Remove Unnecessary Cast a bit smarter in interpolations

Fixes #791: The code '\*' is parsed as MultiLine Comment even with the
presence of the corresponding '*\' in some cases. Hence, OutLining Span
creator should not assume that '*\' will always be present for Multiline
Comment and handle the creation appropriately

Handle AssemblyResolve events when the requesting assembly is unknown

Fix for #565: Syntax node actions are not called for field declarations in compiler analyzer driver if the declaration defines multiple variables

Simplify logic for execution of syntax node actions for field declarations: If there are multiple decls, execute syntax node actions for entire field decl (and its descendants) when processing symbol declared event for first field within it, and skip syntax node actions for rest of fields defined within that declaration.
Current logic is unnecessarily complex in that it tries to execute syntax node actions for individual variable declarators when processing corresponding field symbol declared event, and executes the node actions for shared nodes (e.g. defining type syntax node) when processing first field symbol.

Fine tune analyzer re-analysis trigger during compilation end action computation.

This gets us to the behavior before AnalyzerManager refactoring where we won't perform force analysis of all documents for compiler diagnostic analyzer end action diagnostics.

@heejaechang this should fix the performance regression.

Remove open deployment dependence on telemetry

Fix for internal TFS bug 1128536

When open-only builds of Roslyn are deployed to the RoslynDev hive,
there is no telemetry service hooked up, so we no longer assume one
exists.

This moves the existing tasks into the source repository for Roslyn, as Roslyn
owns the C# and VB MSBuild tasks.

Avoid over-allocation in VB TypeSymbol's
ImplementationForInterfaceMemberMap

Avoid over-allocation in C# TypeSymbol's InterfaceInfo map.

Remove workaround for DevDiv #1004487.

Fix KeyNotFoundException

Fix ReportDiagnosticAnalyzer meta-analyzer to handle broken code case where there are multiple overrides of DiagnosticAnalyzer.SupportedDiagnostics property

Ensure a an operation is a key in the dictionary of operations before
attempting to look it up.

Use TriggerDiagnosticDescriptor in RenameTracking

Fine tune analyzer re-analysis trigger during compilation end action computation. This gets us to the behavior before AnalyzerManager refactoring where we won't perform force analysis of all documents for compiler diagnostic analyzer end action diagnostics.

Fixes #466 "Use a 'TriggerDiagnosticDescriptor' for the rename tracking
diagnostic"

Updates the RenameTrackingDiagnosticAnalyzer to use a
TriggerDiagnosticDescriptor, which prevents the diagnostic title from
appearing in the preview area of the lightbulb. We now pass the
RenameFrom and RenameTo names as part of the Diagnostic's property bag
and construct the localized codefix title based on these in the codefix
itself.