Update minimum Node.js version to 22, updates dependencies

[DaneEveritt]

This PR updates the codebase to support Node 22 as the minimum version and updates many of the dependencies to either their latest version, or the latest version of the defined major grouping. This addresses many of the audit warnings for various security vulnerabilities and should ensure we have an easier time maintaining and upgrading packages down the road since it has been quite some time since things were updated here.

I didn't get a chance to test these changes against most of the server pages because of some Docker annoyances on my local that I need to sort out first.

Other Notes

• Removed TypeScript type checking from the webpack builds and HMR — this slows everything down and is pretty pointless since all modern IDEs do type checking on their own, and we can run tsc --noEmit before builds in CI to verify no issues.
• Removed eslint from the build process as well, for the same reasons above.

Note

There are a bunch of little commits because that was the easiest way to slowly update while checking builds each time. Recommend squash merging this PR into 1.0-develop so it is one update.

[PadowYT2]

As webpack was updated, this change is no longer needed

[nix-shell:~/repos/panel]# node -v
v22.20.0

[nix-shell:~/repos/panel]# yarn build:production
yarn run v1.22.22
$ yarn run clean && cross-env NODE_ENV=production ./node_modules/.bin/webpack --mode production
...
Done in 13.62s.

[rmartinoscar]

Suggested change

	- name: Install dependencies
	run: yarn install --frozen-lockfile
	- name: Build
	run: yarn build:production
	- run: yarn tsc
	- run: yarn lint
	- run: yarn build:production
	- name: Install & Build dependencies
	run: |
	yarn install --frozen-lockfile
	yarn tsc
	yarn lint
	yarn build:production

[rmartinoscar]

Suggested change

	- name: Install dependencies
	run: yarn install --frozen-lockfile
	- run: yarn tsc
	- run: yarn lint
	- name: Build
	run: yarn build:production
	- name: Install & Build dependencies
	run: |
	yarn install --frozen-lockfile
	yarn tsc
	yarn lint
	yarn build:production

[rmartinoscar]

Why use an external library when you already have node:path and you are already using it ?

panel/webpack.config.js

Line 1 in 6d0818d

const path = require('node:path');

panel/webpack.config.js

Line 18 in 6d0818d

path: path.join(__dirname, '/public/assets'),

[PadowYT2]

A package is required here as the node: protocol isn't accessible on the frontend. You would need to polyfill it which needs an external library and in result the asset will be much bigger than just using pathe