fix: skip individual failed Node.js key imports

[MikeMcC399]

• closes I have update my docker to include the lastest keyserver changes in node but get an error from keyserver.ubuntu.com #1386
• responds to build and connectivity issues reported in Realign Node.js signing keys #1382

Situation

When importing Node.js release keys, if a key cannot be imported from the primary keyserver hkps://keys.openpgp.orgs and there is a network connection issue to the fallback keyserver keyserver.ubuntu.com, then importing ALL Node.js keys fails. This in turn causes a build failure, even if the corresponding key, that could not be imported, is not subsequently needed to verify the actual Node.js version selected with NODE_VERSION.

Environment

• cypress/factory:5.11.3
• cypress/factory:5.11.4

Background

As a consequence of catastrophic verification issues with the then Active LTS Node.js version 22.17.0:

• PR fix: prefer Node.js gpg keyserver.ubuntu.com #1377 implemented an emergency workaround to allow releasing cypress/included:14.5.1
• then, following a corresponding fix to the reference repo nodejs/docker-node, PR fix: explicit check for Node.js key import #1380 was implemented which avoided the failure to import a key from hkps://keys.openpgp.org that had been stripped of its identity due to the restriction that an email address can only be a associated with a single key (see hkps://keys.openpgp.orgs FAQ Can I verify more than one key for some email address?)

Change

In factory/installScripts/node/default.sh trap any import failure and log a failure message allowing the workflow instead to continue.

The result is that a network connection issue to the fallback keyserver keyserver.ubuntu.com or similar issue will no longer fail the build at the stage of importing Node.js keys. Instead, the build will fail as a consequence ONLY if there is a failure to import the exact key needed to verify the selected version of Node.js through the NODE_VERSION parameter.

In factory/.env increment FACTORY_VERSION

Environment variable	Before	After
FACTORY_VERSION	5.11.4	5.11.5

[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.