Sync pgxntool to 2.2.0

[jnasbyupgrade]

Summary

• git subtree pull pgxntool from https://github.com/Postgres-Extensions/pgxntool.git release tag, updating the embedded copy from 2.1.0 to 2.2.0. Conflicts resolved by taking upstream's version for every file under pgxntool/ (it's vendored, no local patches to preserve).
• Ran pgxntool/update-setup-files.sh to reconcile setup-copied files against the new version: pruned pgxntool/.claude/ and pgxntool/.github/ (pgxntool's own dev-only tooling, not meant to be embedded in consumer projects). No other setup files (.gitignore, test/deps.sql) needed changes this time.

Verification

• make builds cleanly.
• make install && make installcheck (the same sequence CI's pg-build-test runs) passes all pgTAP tests on PG17, starting from a machine where the extension had never been installed before.

Heads up: found a make test ordering bug in pgxntool 2.2.0 (filed upstream, doesn't block this PR)

While testing locally, make test (not make install && make installcheck) genuinely failed pg_regress (extension "test_factory" is not available) the first time on a machine where the extension had never been installed. Root cause: check-stale-expected (new in 2.2.0, enabled by default) is added to TEST_DEPS before install, but its own prerequisite is installcheck -- so building it pulls installcheck forward, ahead of install, the first time through. A second make test run then passes, since install had already completed.

This repo's CI doesn't use make test/TEST_DEPS at all -- pg-build-test calls make install then make installcheck directly, which is the correct order and is what I re-verified above -- so it's unaffected. It will bite anyone running make test locally on a truly fresh checkout though. Happy to file this against pgxntool separately if useful, distinct from the already-open #49 (installcheck's exit code being swallowed).

Test plan

• make
• make install && make installcheck on a machine with no prior install
• CI (this PR)

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3ba07a4b-70ad-427b-a901-3722f2784866

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}