fix: Improve shrinkwrap generation handling

[d3xter666]

Enhances: #1231

[coveralls]

coverage: 94.69% (+0.1%) from 94.552%
when pulling ce48200 on fix-shrinkwrap-generation
into d0976b0 on main.

[RandomByte]

To verify the shrinkwrap:

npm i
cd packages/cli
node ../../internal/shrinkwrap-extractor/cli.js ../../
rm -rf node_modules # Delete node_modules within CLI package

# <Manually remove devDependencies in package.json>

npm ci --workspaces false

Before Matthias' fix this yielded the following error:

npm error Missing: @npmcli/package-json@7.0.4 from lock file
npm error Missing: @npmcli/package-json@7.0.4 from lock file
npm error Missing: globby@15.0.0 from lock file
npm error Missing: proc-log@6.1.0 from lock file
npm error Missing: proc-log@6.1.0 from lock file
npm error Missing: proc-log@5.0.0 from lock file
npm error Missing: proc-log@5.0.0 from lock file
npm error Missing: unicorn-magic@0.3.0 from lock file

Those dependencies where missing from the shrinkwrap, likely because multiple workspace packages dependent on different versions, overwriting each other.

I'm currently verifying the state after Matthias' fix. I suspect there might still be a problem with dependencies hoisted to the workspace root for packages other than the CLI, conflicting with dependencies of the CLI.

[RandomByte]

I suspect there might still be a problem with dependencies hoisted to the workspace root for packages other than the CLI, conflicting with dependencies of the CLI.

I added a failing test for this case. I'll work on a fix

[RandomByte]

I don't think this will work. If @ui5/target is the root package, it will never search the path node_modules/@ui5/target/node_modules/ for its dependencies.

For module @sapui5/some-thirdparty, the target package would resolve it to node_modules/@sapui5/some-thirdparty, which contains the wrong version now...