Fix two CI-only failures in the get_ctypes regression tests.

The ICU scenario ran unconditionally, but LOCALE_PROVIDER/ICU_LOCALE on
CREATE DATABASE was only added in PostgreSQL 15, so it failed with
"option \"locale_provider\" not recognized" against PG14 in CI.

The builtin scenario probes with a fixed BUILTIN_LOCALE 'C.UTF-8', and
skipped only when template0's own datcollate was exactly 'C' or 'POSIX'.
Several CI runners have template0 already on 'C.UTF-8', which is the
only UTF-8 locale a builtin database can use, so the created database's
locale collided with the template's inherited one and
assertNotIn(self.template_collate, reported) failed spuriously. Skip
that scenario too when template0 is already 'C.UTF-8'.

Author: dpage

web/pgadmin/browser/server_groups/servers/databases/tests/test_db_get_ctypes.py

@@ -116,6 +116,11 @@ def runTest(self):
                 self.skipTest("template0 is %s encoded, so a UTF-8 builtin "
                               "locale cannot be used here."
                               % self.template_encoding)
+            if self.template_collate == 'C.UTF-8':
+                self.skipTest("template0 already uses the 'C.UTF-8' locale, "
+                              "the only one a UTF-8 builtin database can "
+                              "use, so a distinguishable one cannot be "
+                              "created here.")
             self._skip_unless_distinct_template_locale()
             self._create_database("LOCALE_PROVIDER builtin "
                                   "BUILTIN_LOCALE 'C.UTF-8' ENCODING UTF8")
@@ -128,6 +133,9 @@ def runTest(self):
             return
 
         # ICU
+        if self.server_version < 150000:
+            self.skipTest('LOCALE_PROVIDER icu requires PostgreSQL 15 or '
+                          'later.')
         cursor = self.connection.cursor()
         cursor.execute("SELECT 1 FROM pg_catalog.pg_collation "
                        "WHERE collprovider = 'i' LIMIT 1")