Rationalize logging statements across codebase

This fixes up the following problems:
1. Using string concatenation instead of the formatting variant methods.
2. Logging or swallowing exception messages without logging the exception
   itself (this swallows the stack trace).
3. Unnecessary logging on re-thrown exceptions.
4. Unnecessary use of formatting variant methods when not necessary.
5. Complicated logging statements involving significant processing not being
   wrapped inside of a logging level check.
6. Redundant logging both of an exception itself and its message (this is
   unnecessary duplication).
7. Use of the base Logger class instead of our FormattingLogger class.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=182419837

java/google/registry/rde/imports/RdeHostLinkAction.java

@@ -149,9 +149,7 @@ public class RdeHostLinkAction implements Runnable {
           case HOST_NOT_FOUND:
             getContext().incrementCounter("hosts not found");
             logger.severefmt(
-                "Host with name %s and repoid %s not found",
-                xjcHost.getName(),
-                xjcHost.getRoid());
+                "Host with name %s and repoid %s not found", xjcHost.getName(), xjcHost.getRoid());
             break;
           case SUPERORDINATE_DOMAIN_IN_PENDING_DELETE:
             getContext()