Get More Projects onto PGXN

[theory]

Work through the extensions gist and select 50–100 extensions on GitHub. Submit pull requests to add a GitHub workflow to each that publishes the extension on PGXN on release. Some criteria to select extensions:

• Some activity in the last couple years
• Already on PGXN or has a META.json, or just looks useful
• Uses the PGXS build pipeline (PGRX and others are okay too, but the client only does PGXS and Configure)
• Responsive developers (look at issues and PRs)

The contents of the PRs should be:

• A META.json and automate versioning
• A .gitattributes file to exclude non-distributable files from git archive
• A Makefile target to build a distribution (handy for making sure it actually works)
• A GitHub Workflow using pgxn-tools to automate release
• Optionally: A GitHub Workflow using pgxn-tools to test on all supported Postgres versions
• A link to request a PGXN account and the HOWTO for further information
• Instructions for creating GitHub secrets for the PGXN username and password

Some example PRs:

• Add PGXN META.json and test and release workflows pgguru/pg_kaboom#3 (includes test workflow)
• Add PGXN release workflow tembo-io/orb_fdw#2 (includes Makefile targets)
• Add workflow to release on PGXN for a semver tag plv8/plv8#570
• Add PGXN release workflow plv8/pljs#3
• Add PGXN release workflow tembo-io/pg_later#40
• Add PGXN release workflow tembo-io/pgmq#181