fix: prefer Node.js gpg keyserver.ubuntu.com

[MikeMcC399]

• closes Can't check signature of Node.js 22.14.0 or 22.17.0 #1375
• closes Node.js PGP key failure C0D6248439F1D5604AAFFB4021D900FFDB233756 ([email protected]) #1376
• closes Unable to install node 18.12.1 with the cypress/factory #851

Situation

• cypress/factory is unable to build new Docker images that include Node.js versions which have been signed with the key C0D6248439F1D5604AAFFB4021D900FFDB233756

• docker compose reports the error

  16.91 gpg: Signature made Wed Jun 25 00:12:40 2025 UTC
  16.91 gpg:                using RSA key C0D6248439F1D5604AAFFB4021D900FFDB233756
  16.91 gpg: Can't check signature: No public key
  

This also blocks Cypress from releasing any new cypress/browsers or cypress/included image, so long as the Active LTS version has been signed with C0D6248439F1D5604AAFFB4021D900FFDB233756, as is the case with Node.js 22.17.0

Change

• Reverse the keyserver order in

  cypress-docker-images/factory/installScripts/node/default.sh

  Lines 39 to 40 in 08b8bfd

  	gpg --batch --keyserver hkps://keys.openpgp.org $keyserverOptions --recv-keys "$key" || \
  	gpg --batch --keyserver keyserver.ubuntu.com --recv-keys "$key" ; \

• Release cypress/factory:5.11.2

Verification

git clone https://github.com/cypress-io/cypress-docker-images
cd cypress-docker-images
cd factory
docker compose build factory
docker compose build base --no-cache

and ensure that the cypress/base image is built.

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[MikeMcC399]

@AtofStryker

This PR is a prerequisite to releasing the next Cypress version on Docker, which I assume is 14.15.1 planned for today, July 1, 2025.

The key C0D6248439F1D5604AAFFB4021D900FFDB233756 can't otherwise be used for the Active Node.js LTS 22.17.0 release.

A workaround, if this PR is not used, would be to downgrade to the previous Node.js 22.x not signed with this key, which would be Node.js 22.15.1

Another workaround is to import the individual bad key directly from https://github.com/nodejs/release-keys/blob/main/keys/C0D6248439F1D5604AAFFB4021D900FFDB233756.asc

[AtofStryker]

Had a feeling I would run into this today! Thanks @MikeMcC399 going to merge it in