chore: remove unused pnpm overrides

[lyzno1]

Summary

• remove 31 pnpm overrides that no longer affect the current dependency graph
• keep the remaining overrides that are still active or still needed as fresh-resolve safety rails
• regenerate pnpm-lock.yaml so the override set matches the workspace config

Why

A large portion of the workspace-level overrides block was introduced in a batch and is no longer needed for the current lockfile. Keeping those entries adds noise and makes it harder to see which overrides are still intentionally maintained.

Validation

• pnpm install --lockfile-only
• pnpm audit --prod --dev

Impact

This reduces maintenance overhead in pnpm-workspace.yaml without changing the resolved dependency set beyond the override list cleanup.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.75%. Comparing base (63db9a7) to head (3c94897).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #34658   +/-   ##
=======================================
  Coverage   83.75%   83.75%           
=======================================
  Files        4170     4170           
  Lines      176792   176792           
  Branches    35358    35358           
=======================================
+ Hits       148077   148078    +1     
+ Misses      25836    25835    -1     
  Partials     2879     2879           

Flag	Coverage Δ
web	85.45% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.