Use the correct text VKey for HostResource's superordinateDomain (#608)

* Store the superordinateDomain reference as a VKey rather than Key

This is a reference to a Domain object, so we should store it as a VKey
in reference to the Domain table. This should not affect any business
logic, but rather will allow us to set up the SQL tables for
HostResource et al. properly.

db/src/main/resources/sql/schema/db-schema.sql.generated

@@ -195,7 +195,7 @@
         fully_qualified_host_name text,
         last_superordinate_change timestamptz,
         last_transfer_time timestamptz,
-        superordinate_domain bytea,
+        superordinate_domain text,
         primary key (repo_id)
     );
 

db/src/main/resources/sql/schema/nomulus.golden.sql

@@ -316,7 +316,7 @@ CREATE TABLE public."HostResource" (
     fully_qualified_host_name text,
     last_superordinate_change timestamp with time zone,
     last_transfer_time timestamp with time zone,
-    superordinate_domain bytea
+    superordinate_domain text
 );
 
 
@@ -1167,6 +1167,14 @@ ALTER TABLE ONLY public."DomainHost"
     ADD CONSTRAINT fk_domainhost_host_valid FOREIGN KEY (ns_hosts) REFERENCES public."HostResource"(repo_id);
 
 
+--
+-- Name: HostResource fk_host_resource_superordinate_domain; Type: FK CONSTRAINT; Schema: public; Owner: -
+--
+
+ALTER TABLE ONLY public."HostResource"
+    ADD CONSTRAINT fk_host_resource_superordinate_domain FOREIGN KEY (superordinate_domain) REFERENCES public."Domain"(repo_id);
+
+
 --
 -- Name: PollMessage fk_poll_message_contact_repo_id; Type: FK CONSTRAINT; Schema: public; Owner: -
 --