build: Lockfile churn

[alexvy86]

Description

Changes that result from adding a dependency somewhere, doing pnpm i --no-frozen-lockfile, removing the dependency, and doing pnpm i --no-frozen-lockfile again.

Seems to be a lot of churn that the upgrade to pnpm v9 should have applied but didn't. A couple breaking changes in the v9 release notes talk about peer dendencies, which (part of?) this seems to be related to.

Reviewer Guidance

The review process is outlined on this wiki page.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

[tylerbutler]

These changes seem to be expected/OK given my understanding of the pnpm docs, so I'm approving. I don't see any other real options since any dep change seems destined to make these changes. That said, I suggest getting further input before merge.

[alexvy86]

@jason-ha any further thoughts? I'm with Tyler, seems better to merge this on its own so we unblock other changes that touch deps, and investigate the weirdness separately. Unless we expect to be able to resolve it quick, but based on my experiments yesterday and today I don't feel very confident about that (and I'm not spending more time on it right now).

[jason-ha]

I'm okay moving forward - commented in Teams thread.
Might also want a pnpm dedupe when cleaning up, but certainly can be separate.