Update Docker images and frontend dependencies

[Rescla]

Frontend dependencies

I did an update of the frontend dependencies using ncu. I reverted a few updates:

• eslint 10
  • This gave a bunch of extra linting errors which may or may not be valid
• tailwind 4
  • I tried to migrate to the vite plugin and migrate the app using the migration tool, but for some reason it did not recognize all classes so some styling was not loaded correctly.

Node.js Docker image

The version was inconsistent, in the application 22 was used, but the docker image still used 20.

Node.js@20 is old, but 22 is out of active support also (https://endoflife.date/nodejs) so I updated to 24 (latest LTS)

Python Docker image

Minor update from 3.13 to 3.14, but I was also informed by someone that the current docker image contains a bunch of vulnerabilities. I verified this by running trivy. The alpine version does not contain any vulnerabilities, and still works fine. So I changed it.

I ran the e2e and frontend tests fully. I also tried the Docker image, but I could not get the serial mounting to work correctly, so I only checked without radio.

[m4v3r1ckNl]

Thank you for the update.

[jkingsman]

Thanks for the PR! I'm not surprised that serial was misbehaving; Alpine and musl are probably gonna cause issues for us. I'm open to a Node 22-> 24 bump (although security support is still something I'm happy to role with) and the other major bumps (although I'd prefer to update our tests to modern jsdom practices rather than papering over with act, and I'm not sure I love the vite module hacks) , but I'd generally like to keep major lib bumps in their own discrete PRs, and do those one at a time.

I don't want to move from a libc image to a musl image right now unless we can guarantee that all our serial work and cryptor operations are 1:1.

I'd be happy to approve some more modular PRs, one at a time, for the major upgrades, though!