[BUG] Update command gets `workspaces <package name> in filter set, but no workspace folder present`

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

The command npm update -w foo/bar
gets unexpected output
npm WARN workspaces @foo/bar in filter set, but no workspace folder present

This was shown in the output of issue #3960 here.

The warning is confusing. It suggests the workspace is not present or the npm configuration is incorrect.

The result is the same on both Windows and Linux (docker container).

Expected Behavior

It was expected the -w parameters would be processed without warnings.

The update command does complete but that is not initially obvious to the user.

Suppressing the warning would be great. Converting this issue to a documentation change would still be acceptable, making the message and cause visible. The outdated command does not have this issue.

Steps To Reproduce

1. In this environment... anywhere?
2. With this config... default?
3. Run '...'
   npm init
   npm init -w foo/bar (set package name @foo/bar)
   npm install
   npm update -w foo/bar
4. See error...
   npm WARN workspaces @foo/bar in filter set, but no workspace folder present

Environment

• npm: 9.1.1
• Node.js: v19.1.0
• OS Name: windows and linux
• System Model Name: personal build
• npm config: No custom data beyond author

Start by reproducing the warning with the listed npm init, npm init -w foo/bar, npm install, and npm update -w foo/bar commands, then trace how the update command processes the workspace filter. Compare the behavior with outdated and verify that updating @foo/bar completes without the confusing warning, or that the message and cause are documented.