Update Client Deps

[CraigMacomber]

Description

This regenerates the client lock file.

Regenerating the workspace lock file helps detect issues where our dependency specifications are incorrect, as well as provides a way to update our deps to what a customer would get when creating a new project which helps us test more realistic usage.

This found an issue where we have a patch to API extractor, but don't pin the version, so if it gets updated, we can pull in that update breaking the patch. This change pins the version to match the patch since the updates to not include the fix we are patching.

rm ./pnpm-lock.yaml 
rm -r ./node_modules/
pnpm install --no-frozen-lockfile

Reviewer Guidance

The review process is outlined on this wiki page.

Questions:

• Is this a good thing to do now? It made less of an impact than I expected: often we accumulate a ton do duplicated versions and doing this shrinks the install a lot, but it only shrunk a bit this time.

[jason-ha]

Looks like a generally good update to me.
There appear to be more removed packages than added. Some number of needlessly duplicated packages are now consolidated.
Hopefully there are fewer deprecation warning with these updates, but likely we'll need more focused effort to update beyond a number of them.

[CraigMacomber]

Looks like syncpack objects to me setting an override to pin the api extractor version. I guess I need to update the dep in every package instead of using an override. Thats harder to document and a much larger change, but maybe better.

[microsoft-github-policy-service]

This PR has been automatically marked as stale because it has had no activity for 60 days. It will be closed if no further activity occurs within 8 days of this comment. Thank you for your contributions to Fluid Framework!