node-gyp build error when building locally on osx and windows

```
ERROR: /Users/derek/Code/rules_js/BUILD.bazel:10:22: RunBinary node_modules/.aspect_rules_js/bufferutil@4.0.1/node_modules/bufferutil failed: (Exit 1): lifecycle-hooks.sh failed: error executing command bazel-out/darwin_arm64-opt-exec-2B5CBBC6/bin/npm/private/lifecycle/lifecycle-hooks.sh bufferutil ../../../bazel-out/darwin_arm64-fastbuild/bin/external/npm__bufferutil__4.0.1/pkg ... (remaining 1 argument skipped)

Use --sandbox_debug to see verbose messages from the sandbox
/private/var/tmp/_bazel_derek/6745edc468b1987dbcff5df31bdec8bd/sandbox/darwin-sandbox/303/execroot/aspect_rules_js/bazel-out/darwin_arm64-opt-exec-2B5CBBC6/bin/npm/private/lifecycle/lifecycle-hooks.sh.runfiles/aspect_rules_js/npm/private/lifecycle/min/node-gyp-bin/node-gyp: line 5: 1010: command not found
Error: bufferutil@4.0.1 install: `node-gyp-build`
spawn ENOENT
at ChildProcess. (/private/var/tmp/_bazel_derek/6745edc468b1987dbcff5df31bdec8bd/sandbox/darwin-sandbox/303/execroot/aspect_rules_js/bazel-out/darwin_arm64-opt-exec-2B5CBBC6/bin/npm/private/lifecycle/lifecycle-hooks.sh.runfiles/aspect_rules_js/npm/private/lifecycle/min/index.min.js:1:79676)
at ChildProcess.emit (node:events:394:28)
at maybeClose (node:internal/child_process:1064:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) {
code: 'ELIFECYCLE',
errno: 'ENOENT',
syscall: 'spawn',
file: 'sh',
pkgid: 'bufferutil@4.0.1',
stage: 'install',
script: 'node-gyp-build',
pkgname: 'bufferutil'
}

> bufferutil@4.0.1 install /private/var/tmp/_bazel_derek/6745edc468b1987dbcff5df31bdec8bd/sandbox/darwin-sandbox/303/execroot/aspect_rules_js/bazel-out/darwin_arm64-fastbuild/bin/node_modules/.aspect_rules_js/bufferutil@4.0.1/node_modules/bufferutil
> node-gyp-build```

Start by reproducing the bufferutil@4.0.1 failure at BUILD.bazel:10 and inspect the reported lifecycle-hooks.sh, node-gyp-bin/node-gyp, and node-gyp-build entry points. Compare the local macOS and Windows environments, then document or verify a build that completes without the reported spawn ENOENT error.

Written by the indexing model from the issue text.