feat(npm): append corepack hashes when updating package managers

[RahulGautamSingh]

Changes

Add updateArtifacts fn in manager/npm which executes the command corepack use {depName}${newVersion} if a package manager is being updated

Context

Closes: #28335

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository
  pnpm: https://github.com/Rahul-renovate-testing/repro
  yarn: https://github.com/Rahul-renovate-testing/repro-yarn
  npm: https://github.com/Rahul-renovate-testing/repro-npm

[secustor]

LGTM outside of this nitpick and the already mentioned comments.

[viceice]

this hopefully doesn't interfere with the post update function of npm manager when grouping with other updates

[RahulGautamSingh]

this hopefully doesn't interfere with the post update function of npm manager when grouping with other updates

https://github.com/Rahul-renovate-testing/30552-grp-updates
https://github.com/Rahul-renovate-testing/30552-grp-updates-yarn-range
https://github.com/Rahul-renovate-testing/30552-grp-updates-pnpm-range
Checked it here, the lockfile is updated correctly.

[rarkins]

Needs a double/triple check. I'm surprised that adding updateArtifacts() to the npm manager simply works and doesn't cause problems with its other artifacts updating.

[renovate-release]

🎉 This issue has been resolved in version 38.41.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 38.41.0

Your semantic-release bot 📦🚀