.. after merge..

We didn't offer move type to new file if there was a single outer type
in a document with a nested type in it. Move to new file should be
offered for the nested type here.

.. checks identifier checks for rename type.

.. an abstract class. Then, MoveType, RenameFile, RenameType edits are
performed by different subclasses of the editor.

.. Move type tests.

.. naming convention and remove unused ones.

For e.g. double clicking on a class should also show the codeaction.

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.

and export it for both C# and VB. Remove language specific subclasses
that weren't needed.
Also update tests to correctly instantiate the CodeRefactoringProvider
after the change.

AbstractMoveTypeTest

for VisualBasic.

1. organize code
2. remove/reorder signatures
3. reduce fields
4. use expression lambda notation.
5. simplify code

around CodeAction and Editor types.

Reduce the no. of fields stored in State.

with nested private type

Tests for following code actions in C# and VB:
1. Move type to new file
2. Rename type to match filename
3. Rename file to match typename

AbstractMoveTypeTestsBase implements shared helpers for testing MoveType
Refactoring.

CSharpMoveTypeTestsBase and BasicMoveTypeTestsBase contain language
specific test helpers.

Tests are organized as MoveTypeTests.<CodeAction>.cs/vb

where code actions are
Move type to new file
Rename type to match filename
Rename file to match typename etc.

The feature code is mostly language agnostic, so it suffices if we pick
one language and test it heavily and make sure simple things and
language specific parts work as expected, on the other language.

helper to test adding a new document to solution scenarios.

down from AbstractUserDiagnosticTest to
AbstractCodeActionOrUserDiagnosticTest.

CodeAction based refactorings that add new documents,
that are not diagnostic based, such as MoveTypeToFile, need these too.

Most of the logic here is language agnostic, however there are some
differences between the syntax tree structure of C# and VB. Accounting
for these syntactic differences gets VB support working. Move to
new file, Move via UI dialog, Make type partial, all seems to work.

Enable Completion filtering and highlighting by default

Merge telemetry sources into existing projects

Now that the telemetry API is consumable from OSS and the code is there, no
need to have a dedicated binary + vsix for it.