chore(schematics): use node version that works for ts-node

[Lipata]

Seems like a regression in node 22.18.0: nodejs/node#59364

Having a specific 22.17.1 version is a reasonable solution for the moment, because it is expected the issue above to be fixed. Some of the workarounds suggested weren't working (e.g. 76bb3dc). The other solution could be to set the following: https://github.com/balena-io/balena-sdk/pull/1564/files.

Additional information (check all that apply):

• CI/CD

Checklist:

• All relevant tags have been applied to this PR

[Copilot]

Pull Request Overview

This PR addresses a Node.js regression issue in version 22.18.0 that affects ts-node functionality by adding a specific NODE_OPTIONS flag to disable experimental strip-types feature for the schematics test.

• Adds NODE_OPTIONS="--no-experimental-strip-types" specifically for the schematics test command
• Works around a known Node.js 22.18.0 regression that breaks ts-node execution

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The NODE_OPTIONS environment variable is being set both inline for the schematics test and globally in the env section. This creates inconsistent configuration and potential conflicts. Consider either moving the --no-experimental-strip-types flag to the global NODE_OPTIONS or ensuring the inline setting properly overrides the global one.

Suggested change

	NODE_OPTIONS: --max_old_space_size=4096
	npm run test:schematics
	npm run test:i18n
	env:
	NODE_OPTIONS: --max_old_space_size=4096 --no-experimental-strip-types