[Chore] Update to nodejs v22

[art-alexeyenko]

• This PR follows the Contribution Guide
• Changelog updated
• Upgrade guide entry added - TBA

Description / Motivation

Update monorepo and samples to use node 22

• Update engine to node>=22
• Update @types/node deps to 22.9.0
• Update typescript across the board to 5.6.3 for compatibility
  • This also required updates for @typescript-eslint
  • @typescript-eslint plugin updated to version 8, some rules adjusted
  • @stylistic/eslint-plugin-ts dep added to keep using rules removed from @typescript-eslint (💀 Rule deprecations: formatting rules typescript-eslint/typescript-eslint#8072)
  • eslint version has been bumped to 8 for compatibility. v9 introduces some breaking changes in configuration and will be upgraded to later
  • Code adjusted to newer lint rules
• Updates to react, nextjs
  • "cheerio": "1.0.0-rc.3" resolution has been added to prevent test run failing for enzyme (Changes to cheerio exports has broken enzyme enzymejs/enzyme#2609)
  • react and @types/react versions locked to ~18.2 due to some breaking changes in react types for 18.3 when using node 22
• create-sitecore-jss updates
  • upgraded sinon
  • adjusted tests to handle errors correctly for new sinon

Known issue:

• (node:8860) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. error will pop up in console when building packages or apps. This does not affect app execution, and is caused by dependencies of dependencies JSS uses. This error will go away in time, as dependencies are updates (i.e. for http-proxy-middleware Deprecation warnings when using node v22 chimurai/http-proxy-middleware#1058).

Testing Details

• Unit Test Adjusted
• Manual Test/Other (Please elaborate) - build, lint, test, run samples

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

[yavorsk]

Great work!
The changes seem reasonable to me, I also verified build, lint, unit tests on my machine.
The only thing that looks off to me is the @ts-expect-error statements. Maybe we should investigate this deeper in a separate ticket?

[illiakovalenko]

Great job on this update! 👍
Please, review my comments/questions below