switch from hslogger to purpose-built Utility.Debug

This uses a DebugSelector, rather than debug levels, which will allow
for a later option like --debug-from=Process to only
see debuging about running processes.

The module name that contains the thing being debugged is used as the
DebugSelector (in most cases; does not need to be a hard and fast rule).
Debug calls were changed to add that. hslogger did not display
that first parameter to debugM, but the DebugSelector does get
displayed.

Also fastDebug will allow doing debugging in places that are used in
tight loops, with the DebugSelector coming from the Annex Reader
essentially for free. Not done yet.

Command/Move.hs

@@ -5,6 +5,8 @@
  - Licensed under the GNU AGPL version 3 or higher.
  -}
 
+{-# LANGUAGE OverloadedStrings #-}
+
 module Command.Move where
 
 import Command
@@ -18,8 +20,8 @@ import Logs.Presence
 import Logs.Trust
 import Logs.File
 import Annex.NumCopies
+import Utility.Debug
 
-import System.Log.Logger (debugM)
 import qualified Data.ByteString.Char8 as B8
 import qualified Data.ByteString.Lazy as L
 
@@ -175,7 +177,7 @@ toPerform dest removewhen key afile fastcheck isthere = do
 				DropWorse -> faileddrophere setpresentremote
 	showproof proof = "proof: " ++ show proof
 	drophere setpresentremote contentlock reason = do
-		liftIO $ debugM "move" $ unwords
+		liftIO $ debug "Command.Move" $ unwords
 			[ "Dropping from here"
 			, "(" ++ reason ++ ")"
 			]
@@ -255,7 +257,7 @@ fromPerform src removewhen key afile = do
 	showproof proof = "proof: " ++ show proof
 	
 	dropremote reason = do
-		liftIO $ debugM "move" $ unwords
+		liftIO $ debug "Command.Move" $ unwords
 			[ "Dropping from remote"
 			, show src
 			, "(" ++ reason ++ ")"