Avoid unrelated application rebuilds

Based on https://github.com/pnpm/pnpm/issues/4868 we suspect that pnpm's single workspace lockfile will sometimes change in unnecessary ways that invalidate cached builds. This would lead to a monorepo developer making a change in their app, and then some unrelated app gets a new build (and new release, if that's how they configure CI/CD)

Turning off https://pnpm.io/npmrc#shared-workspace-lockfile might be a mitigation.

Start by reading pnpm issue 4868 and the shared-workspace-lockfile configuration documented at pnpm.io/npmrc#shared-workspace-lockfile. Reproduce the suspected unnecessary lockfile changes in a workspace and trace how they invalidate cached builds. Done means an app change no longer rebuilds or releases unrelated applications.

Written by the indexing model from the issue text.