Fixes #12669. Addresses one part of #9674

Fixes both the general code styles page and the naming styles page

This reverts commit 9f30b914.

This reverts commit 12ce69e2.

Reverting this because it is causing VSI test failures, especially around Razor.

This change also introduces Specification and Style management (deleting and editing).

Also, fixes #14358

Explicitly state that suppression state column in error list is only supported for intellisense diagnostics (#13387)

1. Suppression state column shows N/A for build diagnostics.
2. A descriptive tooltip is now shown on error list entries with unsupported suppression state, guiding users to switch to intellisense diagnostics for suppression.

Fixes #11371

and plumb them through the UI, persistence, analyzer/fixer and
other parts of the system. update the simplifier to use the new options.
update codegen features as necessary.

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.