This reverts commit f755e8a8. That
change meant our EditorFeatures code was using DllImports in the
cross-platform binary, and we weren't sure what that would do in
VS for Mac if that code ran. It also brought a dependency on
Microsoft.VisualStudio.RemoteControl, which also seems to depend on
various Windows specific APIs.

We'll finish up the decision of what to do in
https://github.com/dotnet/roslyn/pull/45115

* Move SymbolSearch down to EditorFeatures

* RemoteControl package reference

None of this actually depended on the editor in any meaningful way.

When doing inline rename on a named type (interface, enum, or class) show a checkbox to also rename the file.

The checkbox will always show if the kind supports file rename

The checkbox will be disabled if any of the following is true:
- The type is a partial type with multiple definition locations
- The type does not currently match the file name

Extend ISyntaxFactsService to add IsTypeDeclaration
Implement file rename as part of conflict resolution for inline rename. This will allow other features to do file rename that also use the conflict resolver, all they need to do is set the correct option.

selection handler.

* added partial load mode feature flag and made extract method to handle partial load mode.

when solution is opened in VS, currently we do not know when exactly solution is fully loaded or not. solution explorer might show all files but design time build might not have finished yet so, any semantic operation such as extract method or rename might do wrong thing since it doesn't know that it is dealing with missing information (solution).

we are trying to address this issue with partial load mode, new API platform is working on. basically, we are planning to block most of semantic operations (except completion/quickinfo/goto definition/signature help and navigate to. we might include FAR here as well) during partial load state.

also, for things like squiggle, LB and etc, we will disable those until solution is fully loaded since we don't actually know whether those data is correct or not during partial load state.

this change add featureflag so that we can incrementally add support for each features while dogfooding behavior across partners. as a first attempt, extract method is choosen for new experience.

other internal options are added so that we can try alternative behaviors and etc.

test is not added yet.

* fix merge break

* update string

* small tweak.

* PR feedbacks

* updated the title

* updated after discussing about PR

* do even cheaper version of getting text.

addscope doesn't work with description with blank line when scope is nested. wait dialog seems supporting only 2 lines.

until, I figure out this with platform team, making description one line.

* following PR feedback

Bring EditorFeaturesResources.*.xlf files in line with the current state of EditorFeaturesResources.resx.