TEIIDDES-1917: Addresses refactoring issues with read-only resources

* Rather than disabling refactoring actions if resource is read-only, let
  the refactor wizards handle it.

* If running rename or move, a dialog should be displayed stopping the user
  going any further due to the resource being read-only

* If running any refactoring and a related resource is read-only then the
  dialog will also be displayed

* AbstractRefactorAction
 * Removes restriction on enablement of action due to read-only resources

* RefactorResourceUtils
 * For check methods, pass a level of error status that should be returned.
   Since related resource errors in delete are errors, the deletion of a
   read-only resource is allowed so a warning should be returned
 * In finding related resources, avoid testing their statuses since this is
   checking whether read-only and is unnecessary since these resources are
   tested anyway

* [Delete|Move|Rename]ResourcesRefactoring
 * Better handle distinction between status values returning as warnings
   and errors

* MoveResourcesWizard
 * Corrects extra call to getString() when such strings have already been
   fetched, since the createErrorStatus method is also used for handling
   exception messages