Rename soy templates to use consistent naming scheme

We use {EPP resource}{action} as the naming scheme everywhere else, so we shoudl do so here too.  It's generally nicer for files to group by type of EPP resource (so all of the domain actions are together) than by type of action.

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

java/google/registry/tools/CreateContactCommand.java

@@ -22,13 +22,14 @@ import com.beust.jcommander.Parameters;
 import com.google.template.soy.data.SoyMapData;
 import google.registry.tools.Command.GtechCommand;
 import google.registry.tools.params.PhoneNumberParameter;
-import google.registry.tools.soy.CreateContactSoyInfo;
+import google.registry.tools.soy.ContactCreateSoyInfo;
 import java.util.List;
 import javax.inject.Inject;
 
 /** A command to create a new contact via EPP. */
 @Parameters(separators = " =", commandDescription = "Create a new contact via EPP.")
 final class CreateContactCommand extends MutatingEppToolCommand implements GtechCommand {
+
   // TODO(b/19016175): Expand to allow full suite of contact flows.
   @Parameter(
       names = {"-c", "--client"},
@@ -111,12 +112,10 @@ final class CreateContactCommand extends MutatingEppToolCommand implements Gtech
     if (isNullOrEmpty(password)) {
       password = passwordGenerator.createPassword(PASSWORD_LENGTH);
     }
-
     checkArgument(street == null || street.size() <= 3,
         "Addresses must contain at most 3 street lines.");
 
-    setSoyTemplate(CreateContactSoyInfo.getInstance(),
-        CreateContactSoyInfo.CREATECONTACT);
+    setSoyTemplate(ContactCreateSoyInfo.getInstance(), ContactCreateSoyInfo.CONTACTCREATE);
     addSoyRecord(clientIdentifier, new SoyMapData(
         "id", id,
         "name", name,