Bump `engines` field of `package.json` in `oxlint` and `oxfmt` NPM packages

[overlookmotel]

Currently package.json in npm/oxlint and npm/oxfmt includes:

{
  "engines": {
    "node": ">=8.*"
  },
}

This is inaccurate. NodeJS 8 does not support ESM, which these packages use internally (and #13876 will convertoxlint package to ESM entirely).

Because it's inaccurate already, I think we can consider this a bug fix, rather than a breaking change. Bumping to NodeJS versions which are not EOL I doubt would break many people.

What version?

Ideally, we'd choose minimum versions of Node which support both:

1. require(ESM) - for lazy-loading ESM modules without async (20.19.0+ | 22.12.0+ | >= 24).
2. TS type stripping without experimental flag - for easier support of oxlint plugins written in TS (22.18.0+ | >= 24).

But would requiring Node versions which have both these features be likely to break some users? Probably yes. NodeJS 20 is not EOL until April 2026.

I suggest:

• We go with the versions which support require(ESM) - 20.19.0+ | 22.12.0+ | >= 24.
• Only support oxlint plugins written in TS in 22.18.0+, or use some other package to transform TS.

[Boshen]

@copilot For all package.json files, if it contains a engine field, change it to

  "engines": {
    "node": "^20.19.0 || >=22.12.0"
  },

Ignore all fixtures, generated and test files.