Published packages do not declare the supported Node.js engine

Describe the issue
None of the published packages declare the version of Node.js they support with the engines field in package.json. If this is dictated by dependencies like ESLint, it should be declared and would aid when clients upgrade these dependencies or Node.js. Once ESLint 9 is supported, I think this will be easy to resolve.

• eslint-config-javascript/package.json
• eslint-config-typescript/package.json
• eslint-config-angular/package.json
• eslint-config-playwright/package.json

Not specifying the engines field is technically equivalent to * and means any version. This is not reliable, though. More likely, a package of interest does not support support any version and simply did not declare which versions it does. If a package declares support for specific versions of engines, they can be viewed with the following command.
npm view <package name>[@package version] engines

Start by inspecting the four package.json files named in the issue and compare their dependency requirements with the relevant ESLint package metadata. Use npm view [@package version] engines where useful; done means each published package declares the supported Node.js version range in its engines field.