Rename don't recreate repos on move (Fix #12355)

If a sysadmin properly moves the omero.data.dir to
new location via:

```
  bin/omero config omero.data.dir NEW
  mv OLD NEW
```

then there's no reason that a new repository should
be created. Instead, now a WARN log statement is
printed and the new value should be visible via
`bin/omero fs repos`. Imports of files from before
and after the renaming should work identically.
Remove .lock file on server shutdown.

This should be a minimal fix for situations
where FileMaker can't obtain a lock on the .lock
file in ManagedRepository.
Update the "No FS!" message.
Try to overtake .lock file.
Make ImportLibrary error message universal.
Don't try/catch where it's not needed.
Add dot when if a dialog is going to be opened.
Replace Colour by Color in text displayed to user.

Conflicts:
	components/insight/SRC/org/openmicroscopy/shoola/agents/measurement/util/model/AnnotationDescription.java
	components/insight/SRC/org/openmicroscopy/shoola/util/ui/colourpicker/TabbedPaneUI.java
Fix LegacyRepositoryUnitTest.java.
Add unit test for repository takeover.
Clear the inspector tab.
Make sure to use absolute path.
Merge pull request #2684 from joshmoore/rebased/develop/12355-move-dir

Rename don't recreate repos on move (Fix #12355) (rebased onto develop)
Merge pull request #2690 from jburel/roi-clean-up-develop

Roi clean up develop
Merge pull request #2698 from jburel/rebased/develop/roi-deselect

Clear the inspector tab. (rebased onto develop)
Remove unnecessary try/catch/throw.
Fix LegacyRepositoryUnitTest.java.
Merge pull request #2700 from bpindelski/12359_repo_lock

Acquire repository lock forcefully (fix #12359).