[BUG] legacy-bundling=true breaks transitive dependencies

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

.npmrc:

package-lock=false
legacy-bundling=true

package.json:

{
  "dependencies": {
    "tap": "^15.1.1"
  }
}

❯ npm ls fs.realpath
npm-bundling-test@ /private/tmp/18/npm-bundling-test
└─┬ tap@15.1.1
  ├── fs.realpath@1.0.0 extraneous
  └─┬ glob@7.2.0
    └── fs.realpath@ invalid: "^1.0.0" from node_modules/tap/node_modules/glob

npm ERR! code ELSPROBLEMS
npm ERR! extraneous: fs.realpath@1.0.0 /private/tmp/18/npm-bundling-test/node_modules/tap/node_modules/fs.realpath
npm ERR! invalid: fs.realpath@ /private/tmp/18/npm-bundling-test/node_modules/tap/node_modules/glob/node_modules/fs.realpath

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/jsumners/.npm/_logs/2021-11-18T15_26_46_008Z-debug.log

Expected Behavior

When installing packages with legacy-bundling=true, transitive dependencies should not result in the npm error code ELSPROBLEMS.

Steps To Reproduce

1. Node LTS v16.13.0
2. See "Current Behavior" above
3. npm install && npm ls fs.realpath
4. See error...

Environment

• npm: 8.1.0
• Node: 16.13.0
• OS: 12.0.1
• platform: macOS
• npm config:

; "project" config from /private/tmp/18/npm-bundling-test/.npmrc

legacy-bundling = true 
package-lock = false 

; node bin location = /Users/jsumners/n/bin/node
; cwd = /private/tmp/18/npm-bundling-test
; HOME = /Users/jsumners
; Run `npm config ls -l` to show all defaults.

Start by reproducing the report with the shown .npmrc and package.json, then run npm install && npm ls fs.realpath using the listed Node and npm versions. Trace the legacy-bundling installation and dependency-tree handling until the transitive fs.realpath entries are processed. Done means the reproduction no longer reports ELSPROBLEMS.