ERR_PNPM_LOCKFILE_CONFIG_MISMATCH when using pnpm workspace with named catalogs

[FabienDehopre]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

43.91.5

Please tell us more about your question or problem

when updating npm package(s) for non-major version bump and when using a pnpm workspace with named catalogs, renovate only updates the lock file, not the related catalog entry in the workspace file.
then, when the CI workflow runs the pnpm install --frozen-lockfile command, it errors out with the following message:

ERR_PNPM_LOCKFILE_CONFIG_MISMATCH  Cannot proceed with the frozen installation. The current "catalogs" configuration doesn't match the value found in the lockfile.

Update your lockfile using "pnpm install --no-frozen-lockfile"

there is already a discussion #38610 about the same issue but it is closed and locked so I open this one to see if this can be fixed.

Logs (if relevant)

the error occurs in the CI workflow after the update has already been done by renovate app

[FabienDehopre]

It looks like that the renovate app is adding the update in the wrong catalog file.
Here is what I've found after having manually fixed the lock file:

It added the update in the default catalog instead of the named one I use in the workspace file (prod catalog).
The fix I applied was to update the package version number in the named catalog (in pnpm-workspace.yml) then I run the pnpm install --no-frozen-lockfile in order to update the lock file accordingly.

[FabienDehopre]

might be related to #41731 but the other way around.