[Dependencies] Update to resolve install warnings (after beta rebase)

[flx-sta]

What are the changes?

As requested by @Tempo-anon I've cleaned the dependencies up.
Meaning version bumps, remove unused etc.

closes #2353
duplicate of #3160

ℹ️ After merging this

we should consider adding dependabot to the project
see #2433

Why am I doing these changes?

Mainly to close vulnerabilities and to resolve warnings thrown during the npm i run.

What did change?

1. ⬆️ bump up vitest and eslint version to resolve inflight warning
   • ❌ remove and disable eslint-plugin-import due to not supporting eslint@9 yet (can be reactivated later)
   • ⬆️ bump eslint to 9.7.0.
     • ⬆️ bump @typescript-eslint/eslint-plugin to 8.0.0-alpha.54
     • ⬆️ update @typescript-eslint/parser to 8.0.0-alpha.54
     • ⬆️ update typescript-eslint to 8.0.0-alpha.54
     • ❌ remove eslint-plugin-import as it's not compatible with eslint 9 yet => see Support eslint v9 import-js/eslint-plugin-import#2948
   • ⬆️ update vitest to 2.0.4
     • ⬆️ update @vitest/coverage-istanbul to 2.0.4
2. ❌ remove vite-plugin-fs dependency
   • removed api-generatort-script.ts file (this was in consultations with devs discord-message)
3. ⬆️ bump vite to version 5
4. 🔀 migrate some typescript-eslint to @stylistic/eslint-plugin-ts
   • as stated here: https://typescript-eslint.io/blog/deprecating-formatting-rules#upgrading-to-eslint-stylistic
5. ❌ delete pokenode-ts dependency (unused)
6. ❌ remove axios and axios-cache-interceptor dependency (unused, DOM integrated fetch is being used)
7. ❌ remove unused json-beautify dependency
8. 🔁 move dependency-cruiser to dev dependencies

Screenshots/Videos

How to test the changes?

• run npm i or npm ci => no warnings. No vulnerabilities.
• run npm run build => should still work as expected
• run npm run test:silent => shouldn't fail
• run npm run docs => no errors (plenty of warnings. That's normal)
• run npm run eslint-ci => no warnings
• run npm run start => should start as expected

Checklist

• I'm using beta as my base branch
• There is no overlap with another PR?
• The PR is self-contained and cannot be split into smaller PRs?
• Have I provided a clear explanation of the changes?
• [] Have I considered writing automated tests for the issue?
• Have I tested the changes (manually)?
  • Are all unit tests still passing? (npm run test)
• [] Are the changes visual?
  • [] Have I provided screenshots/videos of the changes?