Mixed version tests for citus

[eaydingol]

Adds support for running regression tests in mixed‑version scenarios

This PR updates the regression test runner script, test schedules, and some regression tests to support running Citus in mixed‑version setups.
With these changes, regression test schedules can be executed in N/N‑1 and mixed‑version scenarios, including:

• SQL version is N‑1
• Library version is N‑1
• A worker is N‑1
• Coordinator is N‑1

For potential usage, see the workflow jobs removed in commit (0642595) and the corresponding test runs at (https://github.com/citusdata/citus/actions/runs/20746079664).

Details

Schedule refactoring
To enable N‑1 testing for the remaining multi‑node tests, this PR separates tests that drop/create the Citus extension from the existing multi_1_schedule into a new schedule multi_1_create_citus_schedule

This allows the remaining multi‑node tests to be reused safely in N‑1 scenarios.

Test changes

• Cleanup steps after tests.
• Minor adjustments to account for the updated schedule structure.

Perl script changes
This PR extends src/test/regress/pg_regress_multi.pl to support:

• Creating the Citus extension at a specific version for the coordinator (the original PR that introduced versioned extension creation updated only worker logic and missed the coordinator Workflow refactor  #8361)
• Changing the Citus library (citus.so) for specific nodes (worker, coordinator, or all)
• Creating the Citus extension at a given version for specific nodes (worker, coordinator, or all)

These changes enable running N/N‑1 compatibility tests in multiple configurations. Sample scenarios are listed below.

Sample scenarios
To demonstrate potential usage sample jobs are added to git workflow but excluded from this PR (see previous comment on the commit and runs).

Test Citus Lib N‑1
All nodes load citus.so from version 13.2.
Test Citus SQL N‑1
All nodes create the Citus extension at version 13.2‑1.
Test Citus Worker N‑1
Only worker 1 loads citus.so from 13.2 and creates the extension at 13.2‑1.
Test Citus Coordinator N‑1
Only the coordinator loads citus.so from 13.2 and creates the extension at 13.2‑1.

Note that the following schedules from “Test Citus” are not included in N‑1 scenarios:

check-multi-1-create-citus, check-multi-mx Some tests in these schedules drop and recreate the Citus extension using the default version, which is incompatible with N‑1 setups.
check-vanilla The test preparation steps have not yet been adapted for N‑1 workflows.

Local testing
Local testing can be performed using sql/versions.sql and test_versions.sh. (removed in previous commit)
Steps:

• Install the citus 13.2
• Copy citus.so files from 13.2.0 to ~/citus-libs/17/v13.2.0
• Install the version from head
• Run ./test_versions.sh

See version_test_results.txt for example results.
Sample test runs:
CITUSLIBDIR=~/citus-libs/17/v13.2.0 CITUSVERSION=13.2-1 N1MODE=workeronly EXTRA_TESTS=versions make check-minimal
CITUSVERSION=13.2-1 N1MODE=all EXTRA_TESTS=versions make check-minimal

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.90%. Comparing base (e1875b9) to head (fa1318d).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8431      +/-   ##
==========================================
- Coverage   88.91%   88.90%   -0.02%     
==========================================
  Files         286      286              
  Lines       63103    63103              
  Branches     7908     7908              
==========================================
- Hits        56110    56100      -10     
- Misses       4735     4739       +4     
- Partials     2258     2264       +6     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[onurctirtir]

LGTM, optionally, we can make CI happier by adding this into multi_name_resolution.sql

SET client_min_messages TO WARNING;

before the following line

DROP SCHEMA multi_name_resolution CASCADE;

Also, I got confused a bit - won't we add a workflow that can be manually triggered via Actions tab within this PR? Sth that takes Citus version and "n-1 mode" to test against as inputs?

--

Also, it'd be nicer if we can document how to run those tests locally / on CI in src/test/regress/README.md etc.