Fixes #36030 - Ensure HStore is enabled

Pulpcore 3.22 will start using HStore[1], which is in
postgresql-contrib. This ensures it's installed and enabled on the DB.
That needs to be done by a super user, so it can't be done in regular DB
migrations.

[1]: pulp/pulpcore#3427

manifests/database.pp

@@ -6,6 +6,7 @@
   if $pulpcore::postgresql_manage_db {
     include postgresql::client
     include postgresql::server
+    include postgresql::server::contrib
     postgresql::server::db { $pulpcore::postgresql_db_name:
       user     => $pulpcore::postgresql_db_user,
       password => postgresql::postgresql_password($pulpcore::user, $pulpcore::postgresql_db_password),
@@ -14,6 +15,12 @@
       before   => Pulpcore::Admin['migrate --noinput'],
     }
 
+    postgresql::server::extension { "hstore for ${pulpcore::postgresql_db_name}":
+      database  => $pulpcore::postgresql_db_name,
+      extension => 'hstore',
+      require   => Class['postgresql::server::contrib'],
+    }
+
     # pulpcore-content fails to reconnect to the database, so schedule a restart whenever the db changes
     # see https://pulp.plan.io/issues/9276 for details
     Class['postgresql::server::service'] ~> Service['pulpcore-content.service']