chore: upgrade to Node.js 22 LTS

[safaiyeh]

Summary

Upgrades the repository to use Node.js 22 LTS (the current Long-Term Support version).

Changes

File	Before	After
.nvmrc	lts/fermium (Node 14)	22
package.json	No engines field	"engines": { "node": ">=22" }
example/package.json	"node": ">=18"	"node": ">=22"
.github/workflows/codeql.yml	node-version: "lts/*"	node-version: "22"

Why

• Node.js 14 (Fermium) reached end-of-life in April 2023
• Node.js 22 is the current LTS version (codename "Jod")
• Explicit version in CI ensures reproducible builds

[greptile-apps]

Greptile Summary

This PR cleanly upgrades the project from Node.js 14 (EOL April 2023) to Node.js 22 LTS. All changes are consistent and properly updated across configuration files.

Key Changes:

• .nvmrc: lts/fermium → 22
• package.json: Added engines.node: ">=22"
• example/package.json: Updated engines.node from >=18 to >=22
• .github/workflows/codeql.yml: Pinned to explicit version 22 for reproducible CI builds

Note: .circleci/config.yml still uses Node 20.18.3 (lines 9, 19, 31, 43) and should be updated in a follow-up to maintain consistency across all CI environments.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• All Node.js version updates are straightforward and consistent across configuration files. React Native 0.76.2, TypeScript 5.6.3, and ESLint 9.20.1 all support Node.js 22. The changes are well-documented and align with the stated goal of upgrading to the current LTS version.
• No files require special attention

Important Files Changed

Filename	Overview
.nvmrc	Updated from Node 14 (lts/fermium) to Node 22, aligning with modern LTS version
package.json	Added engines field with node: >=22 requirement
example/package.json	Updated engines.node from >=18 to >=22
.github/workflows/codeql.yml	Updated Node.js version from lts/* to explicit 22 for reproducible builds