Is your proposal related to a problem?

Node 22 is now the official LTS (Long Term Support) release and we should aim to update our tooling to ensure we are on the latest LTS.

• https://nodejs.org/en/blog/release/v22.11.0
• https://nodejs.org/en/blog/announcements/v22-release-announce (original Node 22 release announcement)
• Node.js release policy

Describe the solution you'd like

Update our references to Node to ensure they change to 22 or where appropriate 22.11 or https://deb.nodesource.com/setup_22.x.

We should try to update this across local development, CI and related Wagatil development repos for a better contributor experience.

• Wagtail core Update to Node 22 (active LTS) & NPM security/minor patches updates #12539
• Wagtail Docker develop Update to Node 22 (active LTS) docker-wagtail-develop#80
• Wagtail Vagrant develop Update to Node 22 (active LTS) vagrant-wagtail-develop#40
• Sphinx Wagtail theme Update to Node 22 (active LTS) sphinx-wagtail-theme#300
• Bakerydemo Update to Node 22 (active LTS) bakerydemo#513
• Eslint config Update to Node 22 (active LTS) eslint-config-wagtail#26
• Stylelint config Update to Node 22 (active LTS) stylelint-config-wagtail#46

Additional context

See previous issues & PRs that have done similar updates

• Upgrade to Node 20 #11141
• Upgrade to Node 18 & formally adopt FNM - (Post Wagtail 4.0) #8499
• Adopt Node 18 & standardise on fnm for Node version management #9148

Working on this

• Anyone can contribute to this, however, you must ensure you can test updates locally and have run them locally before raising a PR.
• View our contributing guidelines, add a comment to the issue once you’re ready to start.
• If you raise a PR or Issue in other repos, please cross-reference this issue.