418 update to typescript 5 & update @vue/tsconfig

[vin-ni]

1. Updated the frontends to typescript 5
2. Updated @vue/tsconfig to fix the importsNotUsedAsValues bug
3. Updated typescript configs based on new @vue/tsconfig routes
4. Fixed element-plus import / compiler settings with info from [TypeScript] [message, message-box] when tsconfig.json set moduleResolution to nodenext or bundler, ElMessage can not be imported. element-plus/element-plus#11818

[github-actions]

File	Coverage
All files	82%	✅
gencaster/distributor.py	69%	✅
gencaster/schema.py	70%	✅
gencaster/urls.py	77%	✅
osc_server/models.py	91%	✅
osc_server/server.py	55%	✅
story_graph/engine.py	72%	✅
story_graph/markdown_parser.py	85%	✅
story_graph/models.py	98%	✅
story_graph/types.py	99%	✅
stream/models.py	91%	✅
stream/types.py	98%	✅

Minimum allowed coverage is 50%

Generated by 🐒 cobertura-action against 1b623c4

[capital-G]

I am not too sure that node is the proper resolution method when reading the changelog of ts5.

It seems node is somehow deprecated and should be used for comparability if one writes a library.

[capital-G]

Citing https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#moduleresolution-bundler

If you are using a modern bundler like Vite, esbuild, swc, Webpack, Parcel, and others that implement a hybrid lookup strategy, the new bundler option should be a good fit for you.

As we are using Vite we should maybe use bundler? :) But I don't understand too much of it I must admit.

[capital-G]

Sorry, just readt the referenced issue - this seems a bug in ElementPlus, so maybe block the upgrade to TS5 until they have EP fixed their bug for TS5? Or is it necessary to upgrade to TS5? Switching to node resolution seems like a hack to me if TS advises to use bundler, especially since node seems somehow deprecated in favour of nodenext?

[vin-ni]

Let's put it on hold then