Document any delay of moving selector caches (eg. `runtime: node@lts`) after release of new versions

actions/setup-node has significant delays (up to 1 month!) of lts/* aliases (cache invalidation bug), due to slow updates in actions/runner-images:

• https://github.com/actions/setup-node/issues/1236
• older issue, with a few more details: https://github.com/actions/setup-node/issues/1236

Does pnpm/setup also suffer from the same delays due to caching? I noticed this wording, which sounds familiar to the explanations by the actions/setup-node team:

a moving selector such as node@lts is reported and cached under the version it resolved to

https://github.com/pnpm/setup/blob/703c52620218391530e48b9e8870d5c0082e1b9b/src/install-runtime/index.ts#L61-L64

If there are any delays, these should be documented.

But if pnpm/setup does not suffer from cache invalidation problems like the actions/setup-node problem, then I would propose it also in those two issues above as an alternative to actions/setup-node.

Start with src/install-runtime/index.ts at lines 61-64 and review the linked actions/setup-node issues for the described cache behavior. Determine whether moving selectors such as node@lts experience delays in pnpm/setup, then document the observed behavior and any delay details or clarify that the issue does not apply.