Fix non-interactive PGDG key import in Release pgrx jobs

[Copilot]

Release workflow jobs pgrx Checks · PG17 (and sibling PG matrix jobs) were failing during PostgreSQL dependency setup before any pgrx build/test steps ran. Root cause was gpg --dearmor requiring TTY interaction on hosted runners.

• Workflow fix: make PGDG key import CI-safe

  • Updated .github/workflows/release.yml in both Linux PostgreSQL install blocks (pgrx Checks and Linux release build job matrix).
  • Added non-interactive flags to GPG key dearmor command so key import works in headless GitHub Actions environments.

• Behavioral impact

  • Unblocks pgrx Checks · PG17 at package-repo setup stage.
  • Prevents the same /dev/tty failure mode across PG15/PG16 and Linux release matrix jobs using the same key import pattern.

curl -fsSL https://www.postgresql.org/media/keys/ACCC4CF8.asc \
  | sudo gpg --batch --yes --dearmor -o /usr/share/postgresql-common/pgdg/apt.postgresql.org.gpg