this gives an ability for host (vs) to talk to remote host (service hub)

Cut the following features:
1. Move type dialog
2. Make type partial.

Trimming the feature set being offered, targeting core scenarios and
dropping fringe features.

Extract Interface (fixes #9958)
- Read textbox labels
- Read extractable members

Generate Type (fixes #9959)
- Read label text on dropdowns
- Read combobox items

Change Signature (fixes #9957)
- Read parameter and button text

Options pages (fixes #9962)
- Read labels/checkboxes/radiobuttons

Revert "Revert "Disable diagnostic service for projects that we know we don't have all information to provide good results.""

Revert "Disable diagnostic service for projects that we know we don't have all information to provide good results."

Implements #7064

This change includes:

- An analyzer and codefix for enforcing naming styles and fixing symbol names to comply with a chosen & configurable set of naming rules.
- A set of Enforcement Levels that can be applied to different naming rules.
- A mechanism for linking from a lightbulb preview to the option that caused the related diagnostic to be created (could be moved to a different PR or release)
- Moving of the "Formatting" options pages under the Code Style node.

Jason believe checking missing metadata in place in FinalizeCompilation shouldn't be that much perf impact and I asked tomas and he agree. so my implementation might have been just me paranoid about allocations and perf regression.

removed tracking and just do simple check in FinalizeCompilation.

Jason left feedback on devdiv side PR about active config change which I didn't thought of before.

so, I tested it and it surfaced some issues. first is, doing reload projects on intellisense build failure can be expensive in some cases, since we already in push mode for workspace events. so, I implemented all the plumbing so that we can just update that one bit.

another issue I found is that, when there is cross language p2p reference A -> B. if B fails on intellisense build, B basically has no information including output path, which means it will not be resolved as cross language p2p reference to A. so, for A's point of view, there is no missing information and think it is fully loaded (since A don't consider B as its dependency), it just thinks one of its file reference (B's output path) is missing. so we end up again shows bunch of errors.

there was no way to resolve this issue except tracking missing metadata reference, so I tried to find cheapest way to track this as much as I can. since we are snapshot model, and file is external to us, I couldnt find a solution which is 100% bullet proof except we checking it every time we create compilation but that is too expensive for the code path. so I check file at the metadata entry point. and rely on our file change notification to correct itself if snapshot become out of sync with reality.

this should fix this another cross language reference issue.

this should make roslyn to turn off full project diagnostics when intellisense build is failed for the project.

when we detect intellisense build failure, VS should put actionable data in error list detail pane.
also bing search for the issue should work as well if one prefer blogs.

this change also fix some issue on cross language p2p references. before there was case where we fail to connect cross language p2p reference causing a lot of errors.

this change also include bulk diagnostic update events improvement. this should let us to deal better (especially when we clean those up) when there are a lot of diagnostics.

ResetInteractive base class is not coupled to VS and therefore is much easier to test.

now we will show <Unknown> for such project.

now, we will automatically re-enable full solution analysis (if user didn't explicitly disabled it) when new solution is opened.

user can either explicitly turn it back on or re-start VS to re-enable the full solution analysis.

By design, dependencies of analyzers must be specified explicitly to ensure that builds are consistent. However, this is surprising and the warning that is generated when a dependency is missing does not give any hints as to how the problem might be solved. I updated the warning to clearly explain what must be done to resolve it.

Old warning: "Analyzer assembly '{0}' depends on '{1}' but it was not found. Analyzers may not run correctly."
New warning: "Analyzer assembly '{0}' depends on '{1}' but it was not found. Analyzers may not run correctly unless the missing assembly is added as an analyzer reference as well."

Fixes #4057

Add support for adding/removing suppressions for diagnostics with no source location. Additionally,  when the diagnostics being suppressed or unsuppressed are across different languages, instead of showing a preview changes dialog per-language, we now show a single preview changes dialog for the entire changed solution.

This change enables "Remove Suppression(s)" context menu command in the error list to enable bulk selecting suppressed issues and removing the suppressions on them.

1. Add IVisualStudioDiagnosticListSuppressionStateService to maintain information about the suppression state of specific set of items in the error list. This service will be used by error list context menu command handlers to query available commands and also used by the fix service.

2. Add IVisualStudioSuppressionFixService to allow adding or removing bulk suppressions (in source or suppressions file), optionally filtered to a specific project. This command will be used by all baselining scenarios to compute diagnostics and apply bulk suppressions fix.

3. Add a SuppressionStateEventProcessor to process selection changed events in the error list and update the suppression state service information.

Fixes #3805 and #2990

now user has a easy way to see just errors from build. the content should be exactly same as what output build window shows.

this change set also includes several misc changes such as adding support for error source and build tool.

This commit updates the `AnalyzerDependencyChecker` type to reflect the
recent changes to require all analyzers and dependencies to be
specified, and the changes in how we load analyzer assemblies.

Now that we require all analyzers and dependencies to be specified, we
no longer look next to the specified analyzers to optimistically locate
dependencies. Instead, we only consider the list of passed-in analyzers
*plus* the assemblies already loaded into the `AppDomain`. The latter
avoids unhelpful warnings in the event that the analyzer assembly
includes a code fix that take a dependency on a Visual Studio assembly,
which of course can't be included in the list of analyzers. We now
create a warning when we identify a missing dependency.

We now also check analyzers themselves for conflicts (i.e., assemblies
at different paths with the same identity but different contents)
instead of just their dependencies.

The RoslynPackage type originally lived in a seperate assembly than
Microsoft.VisualStudio.LanguageServices when it was important for us
to be able to support the core parts of Roslyn being installed atop
the existing Visual Studio 2013 language services. This is no longer
a supported scenario anywhere, so we should just get rid of the
assembly.

Doing this is easy, it's just a matter of moving the files and related
assets to the LanguageServices assembly. A MEF interface is added
to prevent a circularity around triggering a load of stuff in the
SolutionExplorerShim. That could be delt with later by moving the core
of that code back to LanguageServices, but I don't want to touch that
now since it's very sensitive.

Fixes internal TFS bug 1043580.

Display a tooltip containing url destination for hyperlinks in the error list and light bulb preview pane UIs.

Also use full fidelity (i.e. substituted)  error message in the search query in the case of hyperlinks that redirect to bing search so that we can present more relevant search results.