* Both columns added

* Genericize custom column names

* More changes to genericize

* Cleanup

* Respond to feedback

* WIP

* Change tuple to properties

* Restrict to just containing types

* Cleanup

* cleanup

* Refactor

* Change method for getting Containing Type and Member

* refactor GetAdditionalProperties

* Fix merge conflicts

* respond to feedback

* respond to feedback

* Change to struct

* Add type for AbstractCustomColumnDefinitionWithMultipleValues

* Cleanup

* Change AdditionalProperty to FindUsagesProperty

* respond to feedback

* respond to feedback

* Hide columns in F#

* respond to feedback

* fix merge conflict

* Change from hiding columns to removing columns for non supported langs

* Add additional implementations

* formatting

changed our task center status bar to say "low priority background process" rather than "live analysis" to reduce confusion on what "live analysis" means since term "live analysis" has strong association with "errors" in VS.

also, it now shows ## of pending work and whether BG process is paused or not.

At this point, the flighting controls we have aren't really useful
anymore: we want this on for everybody unless the opt out, and that
opt-out would be specific to certain users that are running into issues
with the new system to keep them unblocked. I'm keeping this a per-
machine setting (that doesn't roam) because it's really repo or VS
version specific.

Addresses part of https://github.com/dotnet/roslyn-analyzers/issues/2023

This PR converts our current experimental feature that recommends installation of [FxCopAnalyzers VSIX](https://marketplace.visualstudio.com/items?itemName=VisualStudioPlatformTeam.MicrosoftCodeAnalysis2019) into a non-experimental feature that recommends installation of [FxCopAnalyzers NuGet or VSIX](https://docs.microsoft.com/en-us/visualstudio/code-quality/install-fxcop-analyzers?view=vs-2019).
All the experimental checks have been removed, but I have retained all the existing logic about when the infor bar shows up (light bulb invoked on 3 separate days for separate VS sessions).

Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/824308/

In Naming Styles, we previously hadn't been localizing the "Symbol Kinds" list, along with the other two lists there (Accessibilities and Modifiers). We've decided to loc just the "Symbol Kinds" list because the other two lists are exclusively language keywords.

* Wip

* Update more pages

* Formatting

* Respond to feedback

* Add spacing to Formatting General page

* changed the way we report live analysis to task center

previously, we listen to diagnostic service to report progress. problem is that, it only raise event if it found errors on a file. so what we report is actually last file we found errors on rather than file that we are analyzing.

this caused confusion since we report in task center that we are analyzing file "A" when it is actually "analyzed" not "analyzing"

another issue is since it only report file that contains errors. we might not actually show anything in task center if there is no error, or show file "A" for long time if that is only file with errors.

this PR changes the experience closer to what users would expects. and now progress is for solution crawler not specifically on diagnostics.

now we report file that solution crawler is analyzing.

there is still cavet such as solution cralwer can pause between processing a file if VS is busy. but it will still show file "A". or we will not update UI at least 200ms a part and etc.

since it is task center where we don't want to be too impactful to VS, based on feeedback we will see whether we need to do more such as detect solution crawlwer pause and update task center to show pasue. or update task center to show different stage such as analyzing/analyzed.

or show in task center, what analyzer is actually running such as diagnostic, todo, designer attribute scan, find all reference cache and etc.

* addressing PR feedbacks

Restore some resources incorrectly removed from the .xlf files.

Move to namespace allows a user to move all symbols in a context
to a different namespace, whether it's a new one or existing. This is
different from renaming a namespace as not all symbols in the namespace
are moved, only ones within the current document.

It relies on the IChangeNamespaceService implementation to do the heavy
lifting. Since the current implementation only supports C#, this new
feature will as well.

After this is checked in, when a user has the cursor inside a namespace
declaration that has no nested namespace declarations within it, a code
fix will be suggested to pop up a dialog and help the user choose a new
namespace.

* Add a synced use enhanced color checkbox to C# and Basic advanced options.

* Use optionstore in DiagnosticWindow option pages

* Add option search keywords for enhanced color option

This is a reworked version of #32616 targeting the dev16.0-preview3 branch.