[BUG] npm pack fails for scoped package from private registry when it's not in the cache

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

Since version 7.x if the scoped package is not present in the cache the command "npm pack @foo/bar@baz" returns a 404 error.

Refer to this issue : #2918

Expected Behavior

The command "npm pack @foo/bar@baz" work again with scoped package like npm 6.14.

Steps To Reproduce

1. Create package with scope like "@foo/bar" in version 1.0.0
2. On a server that has never installed this package, try using the command "npm pack @foo/bar@1.0.0"
3. A 404 error occurs.
4. However, if you do "npm i @foo/bar@1.0.0" it works without error.
5. Try using the "npm pack @foo/bar@1.0.0" command again
6. it will work without error.
7. now try to use "npm cache clean --force"
8. Try using the "npm pack @foo/bar@1.0.0" command again
9. A 404 error occurs.

Environment

• npm: 8.5.5
• Node.js: 17.8.0
• OS Name: ubuntu (20.04) macos (latest) windows (latest)

Start by reproducing the scoped-package case with npm pack against a private registry, then compare it with npm install and the behavior after npm cache clean --force. Trace the npm CLI entry points for pack, install, and cache handling to identify where the uncached package path diverges. Done means npm pack @foo/bar@1.0.0 succeeds on a clean cache without the 404.