fix(tools-node): limit package dependency search scope

[vivekjm]

Description

Resolves #801.

This adds a stopDir option to findPackageDependencyDir so callers can keep dependency lookup bounded to a repository root instead of walking all the way up the filesystem. The stop directory itself remains part of the search, so root-level node_modules is still found.

A regression test covers both cases: a dependency above stopDir is ignored, while a dependency at stopDir/node_modules is still resolved.

Test plan

• PATH="$HOME/.nvm/versions/node/v22.22.0/bin:$PATH" yarn workspace @rnx-kit/tools-node test
• PATH="$HOME/.nvm/versions/node/v22.22.0/bin:$PATH" yarn workspace @rnx-kit/tools-node build
• PATH="$HOME/.nvm/versions/node/v22.22.0/bin:$PATH" yarn workspace @rnx-kit/tools-node lint
• PATH="$HOME/.nvm/versions/node/v22.22.0/bin:$PATH" yarn change:check

Note: the default local Node v20.15.0 cannot run the repo test command because it lacks fs.globSync; the commands above were run with local Node v22.22.0.

[vivekjm]

Updated in 5918878. I reverted the incidental startDir defaulting change and left the stopAt pass-through/regression coverage intact.

Test note: I ran corepack yarn install --immutable, then attempted corepack yarn workspace @rnx-kit/tools-node test; the local run is blocked because this machine has Node v20.15.0 and the repo test command calls fs.globSync, which is unavailable there.

[tido64]

Thanks! It looks like CI is failing on formatting. Can you run yarn format and push the changes?

Test note: I ran corepack yarn install --immutable, then attempted corepack yarn workspace @rnx-kit/tools-node test; the local run is blocked because this machine has Node v20.15.0 and the repo test command calls fs.globSync, which is unavailable there.

Is there a particular reason for why you can't use Node v22 or greater?