TEIIDDES-1622: Replace the move action

* Convert the refactor move action to use eclipse's LTK API
 * Wires the action into the eclipse refactoring UI dialog / wizard
 * Wires the action into the eclipse history service
 * Wires the action into the undo / redo framework

* Action is no longer confined to a single resource

* LTK refactoring framework uses change objects for encapsulating the
  modify operations.

* AbstractResourceCompositeChange
 * Sub-class of LTK's CompositeChange that is necessary due to the use of
   EMF. Whenever the change is performed, its child change objects are
   first interrogated for any resources and these are unloaded to avoid
   any erroneous EMF validity errors.

* Remaining issue is the undo/redo commands on the Edit menu as these are
  not currently tied into the resource operation stack but only looks at
  the model edit stack
TEIIDDES-1622: Remove the RefactorUndoManager

* Since undo/redo is being wired into the eclipse history, the
  RefactorUndoManager is no longer needed
TEIIDDES-1622: Refactors the ModelerUndoManager

* Instead of model editors and the model view having a separate
  undo/redo history manager, retask the ModelerUndoManager to
  interface with eclipse's operation history.

* This allows the model view to undo/redo refactor-resource changes
  as well as modelling EMF changes.

* Removes the custom undo/redo actions since they are unnecessary.

* Removes the undo/redo actions from the refactor menu as they are
  now unnecessary.

* Plug in the undo/redo actions in the model editor so that the
  global edit commands work when the editors are in focus.
WIP for rename action