Delete end-date sunrise, landrush, and sunrush phases

This also deletes the associated commands and domain application specific
entities.

We haven't used any of these TLD phases since early 2015 and have no
intent to do so in the future, so it makes sense to delete them now so we
don't have to carry them through the Registry 3.0 migration.

Note that, while there are data model changes, there should be no required
data migrations. The fields and entities being removed will simply remain
as orphans. I confirmed that the removed types (such as the SUNRUSH_ADD
GracePeriodType) are no longer used in production data, and left types
that are still used, e.g. BillingEvent.Flag.LANDRUSH or
HistoryEntry.Type.ALLOCATE.

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

java/google/registry/batch/DeleteContactsAndHostsAction.java

@@ -106,13 +106,9 @@ import org.joda.time.Duration;
 
 /**
  * A mapreduce that processes batch asynchronous deletions of contact and host resources by mapping
- * over all domains and domain applications and checking for any references to the contacts/hosts in
- * pending deletion.
+ * over all domains and checking for any references to the contacts/hosts in pending deletion.
  */
-@Action(
-  path = "/_dr/task/deleteContactsAndHosts",
-  auth = Auth.AUTH_INTERNAL_ONLY
-)
+@Action(path = "/_dr/task/deleteContactsAndHosts", auth = Auth.AUTH_INTERNAL_ONLY)
 public class DeleteContactsAndHostsAction implements Runnable {
 
   static final String KIND_CONTACT = getKind(ContactResource.class);