pnpr TS client: skip the resolve exchange when the lockfile already satisfies the manifest

[zkochan]

Port of the Rust-side satisfaction gate from #13905 (issue #13904, proposed change 2) to the TypeScript client.

installViaPnprServer currently reads the existing lockfile only to ship it to the server and always performs the resolve round trip, even when the on-disk lockfile still satisfies every manifest. The local machinery that answers this exists but is only used on the non-pnpr path (allProjectsAreUpToDate / satisfiesPackageManifest, used by the frozen-lockfile validation).

The Rust client now checks satisfaction locally and goes straight to the frozen materialization when nothing needs resolving; the TS client should do the equivalent inside installViaPnprServer (or mutateModulesViaPnpr before calling it): when the existing lockfile satisfies every project and the mutation is a plain install, skip the resolveViaPnprServer call and go headless. Verification can stay cache-first the way the Rust side does — the TS client already records via writeWantedLockfileAndRecordVerified, so a warm lockfile-verified.jsonl covers the input lockfile without a server exchange.

Until this lands, identical pnpm install inputs produce different server-request behavior between the two stacks (same installed tree and lockfile either way).

---

Written by an agent (Claude Code, claude-fable-5).