.. to move or to rename to.

In case of nested types, the accepted style of naming the file is either
by the standalone typename or with a dotted name derived from its type
hierarchy. For e.g: If type B is nested inside type A, acceptable file
names for type B is B.cs or A.B.cs

Offer these as suggested filenames if the file is named something other
than either of these two. These suggestions are then picked up and
surfaced as "Move to.." or "Rename file to.. " code actions.

.. checks identifier checks for rename type.

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

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.

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

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.