refactor: refactor the release workflow's test job to use a GitHub Actions matrix strategy, running PostgreSQL 14-18 tests in parallel instead of sequentially.

[NFUChen]

Summary

Refactor the release workflow's test job to use a GitHub Actions matrix strategy, running PostgreSQL 14-18 tests in parallel instead of sequentially.

Changes

• .github/workflows/release.yml: Replace 5 sequential test steps (one per PG version) with a single matrix-based job that runs all versions in parallel using fail-fast: false.

Benefits

• Faster CI: All 5 PostgreSQL versions test concurrently instead of one after another.
• Cleaner config: Removes ~20 lines of duplicated step definitions.
• Better visibility: Each PG version appears as a separate matrix entry in the GitHub Actions UI, making failures easier to identify.

[greptile-apps]

Greptile Summary

This PR updates the CI and release test workflows to run PostgreSQL coverage through matrix jobs. The main changes are:

• Split PR checks into separate short unit tests and PostgreSQL integration tests.
• Added a PostgreSQL 14-18 matrix for CI integration tests.
• Converted release tests from sequential PostgreSQL steps into a parallel matrix.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed workflow code.

_{Reviews (1): Last reviewed commit: "fix: ensure integration tests depend on ..." | Re-trigger Greptile}

[tianzhou]

Have you tried? The test are heavyweight, running in parallel might exhaust the test container resource

[NFUChen]

Have you tried? The test are heavyweight, running in parallel might exhaust the test container resource

Yes, it works in my forked repo, see job