bugfix: Running move --to with a remote whose UUID was not yet known

* bugfix: Running `move --to` with a remote whose UUID was not yet known
  could result in git-annex not recording on the local side where the
  file was moved to. This could not result in data loss, or even a
  significant problem, since the remote *did* record that it had the file.
* Also, add a general guard to detect attempts to record information
  about repositories with missing UUIDs.

Command/Move.hs

@@ -75,6 +75,7 @@ toStart move file = isAnnexed file $ \(key, _) -> do
 			return $ Just $ toPerform move key
 toPerform :: Bool -> Key -> CommandPerform
 toPerform move key = do
+	Remotes.readConfigs
 	-- checking the remote is expensive, so not done in the start step
 	remote <- Remotes.commandLineRemote
 	isthere <- Remotes.inAnnex remote key