chore: moving to pnpm 11 and removing node 20 support

[jaredwray]

Please check if the PR fulfills these requirements

• Followed the Contributing guidelines and Code of Conduct
• Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
chore: moving to pnpm 11 and removing node 20 support

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (87e6153) to head (f0e04b3).

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #43   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           19        19           
  Branches         1         1           
=========================================
  Hits            19        19           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gemini-code-assist]

Code Review

This pull request performs a major version bump to 2.0.0, updates the package manager to pnpm 11, and adjusts workspace build configurations. The code changes also include a downgrade of Node.js type definitions and a significant cleanup of the lockfile, notably removing jsdom and its associated dependencies. Reviewer feedback recommends adding an engines field to package.json to enforce Node.js version requirements and removing the deprecated onlyBuiltDependencies field in pnpm-workspace.yaml to align with pnpm 11 standards.