Should includedScripts also be configurable from project.json?

[unrevised6419]

Nx reads includedScripts only from a package.json nx field. In project.json it is silently ignored: neither project-schema.json nor nx-schema.json defines it, and no warning is printed.

Our case: a root project.json adds a single target (test:ts) to the workspace root, but the root package.json scripts all wrap nx run-many. Once they are inferred as root-project targets, they recurse: pnpm run test:lint → nx run-many -t test:lint → the root project's test:lint → … Setting "nx": { "includedScripts": [] } in package.json fixes it, but it splits the root project's configuration across two files.

Is package.json-only intentional? If so, feel free to close this. A note in the project.json docs, or a warning when the key appears there, might help others who try it.

Tested on Nx 23.2.1.