feat!: add Node 24 and 26 support, remove 20

[styfle]

Summary

• update CI to test Node 24 and 26 support, remove 20
• move single-run coverage and release jobs from Node.js 20 to Node.js 22
• update Node 26-incompatible integration dependencies and node-gyp
• refresh JWT signing transitive dependencies and adjust the Auth0 integration fixture for the updated SDK
• rebase onto the PNPM-based main, remove yarn.lock, and regenerate pnpm-lock.yaml

Related

• Fixes Make ncc compatible with Node.js >=24 #1308

Testing

• nvm use 26 && pnpm install --frozen-lockfile && pnpm build-test-binary && pnpm build && pnpm test --runInBand
• nvm use 24 && pnpm install --frozen-lockfile && pnpm build-test-binary && pnpm build && pnpm test --runInBand
• nvm use 22 && pnpm install --frozen-lockfile && pnpm build-test-binary && pnpm build && pnpm test --runInBand && pnpm test-coverage

  

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​node-gyp@​12.3.0
	npm/​@​google-cloud/​bigquery@​8.3.1
	npm/​auth0@​4.37.1

View full report

[MikeMcC399]

It looks like you would need to rebase this branch to also use pnpm

The branch protection rule requirement for successful Node.js 20 tests would also need to be removed. (I remember when Node.js 18 needed to be dropped that this was a potential hurdle with IT approvals.)