Updating packages and removing figma

[bapplejax]

Description

Updating several packages and testing locally to ensure no more vulnerabilities.
Removed figma integration as was causing lodash version to have a critical vulnerability.

Motivation and Context

Many packages needed updating at once and moving to Vite major version.

How Has This Been Tested?

Locally running project

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.59%. Comparing base (bb9d830) to head (1e6535b).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #484      +/-   ##
==========================================
- Coverage   99.59%   99.59%   -0.01%     
==========================================
  Files          51       51              
  Lines         997      995       -2     
  Branches      346      344       -2     
==========================================
- Hits          993      991       -2     
  Misses          4        4              

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

[Copilot]

Pull request overview

This PR updates frontend/tooling dependencies to address vulnerabilities, including removing the Figma code-connect integration and moving the build tooling to a new major Vite version.

Changes:

• Remove @figma/code-connect from devDependencies.
• Upgrade Vite and related tooling (including @vitejs/plugin-react) and bump TypeScript.
• Update Storybook’s Vite framework package version.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

publish:ui-kit / unpublish:ui-kit still run npx figma connect ..., but @figma/code-connect has been removed from devDependencies (and there’s no other figma package in the lockfile). These scripts will now fail (or unexpectedly download a package at runtime via npx). Remove these scripts or replace them with the new intended publishing flow/tooling.

[Copilot]

@storybook/react-vite is bumped to 10.3.4, but the root storybook package and most Storybook addons are still pinned to 10.2.13. @storybook/react-vite@10.3.4 has a peerDependency on storybook ^10.3.4, so this version skew can lead to npm peer warnings and runtime incompatibilities. Align the Storybook-related packages to the same release (either all 10.3.4+ or revert @storybook/react-vite to 10.2.13).

[Copilot]

With the Vite/plugin updates, some dependencies now require newer Node versions (e.g., @vitejs/plugin-react@6 declares node ^20.19.0 || >=22.12.0). Consider adding an explicit engines.node constraint in package.json (and/or documenting it) so local dev/CI environments don’t drift onto unsupported Node versions.

[marshyski]

LGTM