Tighten up restrictions on domain/host naming on EPP resources

All domain/host names should be stored in their canonical forms (puny-
coded and lower-cased). This validation is already in the flows, but
this adds protection against bad data from other sources, e.g. admin
consoles or RDE imports.

This also removes an old work-around that temporarily suspended this
validation for superusers, because we used to have non-canonicalized
data in the system. The non-canonicalized data has since all been
cleaned up, so this work-around is no longer necessary.

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

javatests/google/registry/whois/testdata/whois_domain.txt

@@ -1,4 +1,4 @@
-Domain Name: EXAMPLE.tld
+Domain Name: example.tld
 Domain ID: 3-TLD
 WHOIS Server: whois.nic.fakewhois.example
 Referral URL: http://www.referral.example/path
@@ -52,8 +52,8 @@ Tech Phone Ext: 1234
 Tech Fax: +1.5555551213
 Tech Fax Ext: 93
 Tech Email: EMAIL@EXAMPLE.tld
-Name Server: NS01.EXAMPLEREGISTRAR.tld
-Name Server: NS02.EXAMPLEREGISTRAR.tld
+Name Server: ns01.exampleregistrar.tld
+Name Server: ns02.exampleregistrar.tld
 DNSSEC: signedDelegation
 >>> Last update of WHOIS database: 2009-05-29T20:15:00Z <<<
 

javatests/google/registry/whois/testdata/whois_multiple_nameservers.txt

@@ -1,11 +1,11 @@
-Server Name: NS1.EXAMPLE.tld
+Server Name: ns1.example.tld
 IP Address: 192.0.2.123
 IP Address: 2001:db8::1
 Registrar: Example Registrar, Inc.
 WHOIS Server: whois.nic.fakewhois.example
 Referral URL: http://www.referral.example/path
 
-Server Name: NS2.EXAMPLE.tld
+Server Name: ns2.example.tld
 IP Address: 192.0.2.123
 IP Address: 2001:db8::1
 Registrar: Example Registrar, Inc.

javatests/google/registry/whois/testdata/whois_nameserver.txt

@@ -1,4 +1,4 @@
-Server Name: NS1.EXAMPLE.tld
+Server Name: ns1.example.tld
 IP Address: 192.0.2.123
 IP Address: 2001:db8::1
 Registrar: Example Registrar, Inc.