Fix running PG upgrade tests with run_test.py

In #6814 we started using the Python test runner for upgrade tests in
run_test.py, instead of the Perl based one. This had a problem though,
not all tests in minimal_schedule can be run with the Python runner.
This adds a separate minimal schedule for the pg_upgrade tests which
doesn't include the tests that break with the Python runner.

Author: JelteF

src/test/regress/citus_tests/run_test.py

@@ -239,7 +239,7 @@ def default_base_schedule(test_schedule, args):
         return None
 
     if "pg_upgrade" in test_schedule:
-        return "minimal_schedule"
+        return "minimal_pg_upgrade_schedule"
 
     if test_schedule in ARBITRARY_SCHEDULE_NAMES:
         print(f"WARNING: Arbitrary config schedule ({test_schedule}) is not supported.")

src/test/regress/minimal_pg_upgrade_schedule

@@ -0,0 +1 @@
+test: multi_test_helpers multi_test_helpers_superuser multi_test_catalog_views