add remote.<name>.annex-checkuuid

Added remote.<name>.annex-checkuuid config, which can be set to false to
disable the default checking of the uuid of remotes that point to
directories. This can be useful to avoid unncessary drive spin-ups and
automounting.

Note that the UUID check is still done before writing to the repository,
to avoid writing to the wrong repository if it got relocated. Check is
also done before checkPresent to avoid getting confused about what is in
which repo. This is effectively the same as the use of git-annex-shell
with a uuid to check that the remote repository is the expected one.
Did not bother with the check for retrieveKeyFile because it doesn't
matter if the wrong repo is used then.

This commit was sponsored by Trenton Cronholm on Patreon.

doc/bugs/Missing_automounts_block_every_command.mdwn

@@ -42,3 +42,6 @@ Use any git-annex command and wait for at least `x-systemd.device-timeout`:
 ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
 
 I’m very happy with git-annex (thanks) and use it frequently enough to notice this behavior.
+
+> [[fixed|done]] via the `remote.<name>.annex-checkuuid` config setting
+> that can disable this behavior. --[[Joey]]

doc/bugs/Missing_automounts_block_every_command/comment_4_c3cfb1c27806c45dfa6ebf275c175d3e._comment

@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2018-01-10T17:37:42Z"
+ content="""
+Added remote.<name>.annex-checkuuid config, which can be set to false
+to disable the default checking of the uuid. It will still check before
+making any modification of the remote repository.
+
+There may still be situations where using this kind of automount is suboptimal
+with git-annex, as outlined in comment 3, but I think this is as far as it makes
+sense to change git-annex to deal with them.
+"""]]