Upgrade UI packages

[IDisposable]

Move to current on all non-major upgrades

Runtime

Package	From	To
@headlessui/react	2.2.3	2.2.4
@vitejs/plugin-basic-ssl	2.0.0	2.1.0
cva	1.0.0-beta.3	1.0.0-beta.4
focus-trap-react	11.0.3	11.0.4
framer-motion	12.11.5	12.23.0
react-simple-keyboard	3.8.72	3.8.89
tailwind-merge	3.3.0	3.3.1
validator	13.15.0	13.15.15

Dev

Package	From	To
@eslint/compat	1.2.9	1.3.1
@eslint/js	9.26.0	9.30.0
@tailwindcss/postcss	4.1.7	4.1.11
@tailwindcss/vite	4.1.8	4.1.11
@types/react	19.1.4	19.1.8
@types/react-dom	19.1.5	19.1.6
@types/validator	13.15.0	13.15.2
@typescript-eslint/eslint-plugin	8.32.1	8.35.1
@typescript-eslint/parser	8.32.1	8.35.1
@vitejs/plugin-react-swc	3.9.0	3.10.2
eslint	9.26.0	9.30.1
eslint-plugin-import	2.31.0	2.32.0
globals	16.1.0	16.3.0
postcss	8.5.3	8.5.6
prettier-plugin-tailwindcss	0.6.11	0.6.13
tailwindcss	4.1.7	4.1.11

[IDisposable]

Updated to include the (first) current round of dependabot finds.

This set of changes was tested.

It includes all the UI package updates except:

• build(deps): bump zustand from 4.5.7 to 5.0.5 in /ui #581 (because I haven't yet tested the major change to zustand)
• build(deps): bump react-router-dom from 6.30.0 to 7.6.2 in /ui #599 (as I haven't yet tested that major change to react-router-dom)

[IDisposable]

Please hold, something is acting wrong in HDMI detection with the last group of changes (might be the GO side being out of sync) It was that the device wasn't up to 0.4.2

[IDisposable]

@ym rebased and added new changes. Tested on my JetKVM

[IDisposable]

As of this time, upgraded everything except (because they are major changes I haven't tested):

Package	From	To
react-router-dom	6.3.3	7.6.3
recharts	2.15.3	3.0.2
zustand	4.5.2	5.0.6
vite	6.3.5	7.0.0

AFTER this PR is merged, we probably should do these one-at-a-time

[IDisposable]

Added today's set of updates

Package	From	To
framer-motion	12.22.0	12.23.0
react-simple-keyboard	3.8.88	3.8.89
eslint	9.30.0	9.30.1
vite	6.3.5	7.0.0

ALSO Fixes the slower rendering of WebGL video renderer if video settings are at default (1.0) values, eliminating the overhead if the user hasn't requested filter adjustments because doing so breaks hardware rendering on (most) platforms/browsers.

[IDisposable]

@adamshiervani please see this video change that eliminates a browser warning I only noticed while testing this package update set. When #557 was merged, this warning started appearing because we are always setting the filter: attribute. This change ensures that if the current settings are all 1.0 (e.g. the default/no-change) we will not emit the filter: attribute so we don't taint the video WebGL rendering canvas, which means hardware rendering can still be used. This fixes something I saw on the Discord server (and personally noticed) that the video rendering was not as smooth in recent releases.