Let users choose whether pnpm provider updates respect the release-age delay

[Neonsy]

Could we add a provider update setting that lets users choose between updating immediately and respecting pnpm’s minimumReleaseAge policy?

PR #14295 proposes installing the exact version T3 Code advertises, fixing updates that leave the installed version unchanged. That also bypasses pnpm’s default release-age delay. Some users want the newest provider release immediately, while others prefer to keep that delay

The setting could offer two choices:

• Respect pnpm’s release-age policy: Only offer versions eligible under the effective pnpm policy, and explain when a newer release is waiting on the cooldown
• Update immediately: Request the advertised version using the pinned update command, with clear wording about bypassing the default cooldown

The advertised version, Update button, and copyable command should all follow the selected policy, so T3 Code offers the version it intends to install

I’d prefer respecting pnpm’s policy by default, with immediate updates available as an explicit choice. The first version could be limited to providers installed globally through pnpm

Related bug report: #14249