Fix remaining typescript issues, enable tsc

[silverwind]

Fixes 79 typescript errors. Discovered at least two bugs in notifications.ts, and I'm pretty sure this feature was at least partially broken and may still be, I don't really know how to test it.

After this, only like ~10 typescript errors remain in the codebase but those are harder to solve.

[wxiaoguang]

There should be no "tsc" error now

tested: dropzone, tribute, repo search (explore page)

[silverwind]

Those .vue import errors can be fixed by using vue-tsc instead of tsc, but it's currently broken for typescript 5.7 which we already use: vuejs/language-tools#5018.

As for the not callable and not constructable errors in dynamic imports, I'm out of ideas but it must be something with the ts configuration I assume.

[silverwind]

I guess I will just uninstall vue-tsc and we live with those few @ts-expect-error. vue-tsc is essentially monkeypatching tsc and that will likely break again in the future, so I think we are better off using official typescript tooling only.

[silverwind]

tsc is now enabled as part of make lint-js and is passing for me and should do too on CI.

Edit: Yes, it's passing, so this is ready.

[silverwind]

I switched back to vue-tsc, to a fork of mine that is from their master branch which works with typescript 5.7, but for some reason was not released yet (see vuejs/language-tools#5018).

.vue files are getting type-checked again and the errors on the imports on .vue files go away. Interestingly a new error shows in vitest.config.ts, so I added a @ts-expect-error there. I hope we can resolve this later.

[silverwind]

FYI I opened vitejs/vite-plugin-vue#487 regarding this not callable error.

[silverwind]

So I think I found the magic incantation that requires the least amount of @ts-expect-error. It's from the vite vue+ts template:

    "module": "esnext",
    "moduleResolution": "bundler",

This is a bit suboptimal as we do have a few node.js scripts, but we can likely split the tsconfig into two later, one for node files and one for web_src, but I will defer that to another PR amd this is ready to merge.

[silverwind]

I added type definitions for all named exports from *.vue files, so npx tsc is now also clean. tsc does not typecheck the .vue files because it can not parse them, so we still need to use vue-tsc for that.

Long-term, I'd like to forbid named exports from Vue SFCs, they just don't seem worth it when these functions can easily live outside. Should be possible with eslint.