Vue3 migrate

[femans]

This migrates to vue3, vuetify3Beta, vuex4, Vite, Vitest, TS support, prettier
Fixing #125 and #124

Cycled in extra features:

• iframe component with loading spinner
• Allow opening detail links in a new tab #132 links to detail page are now actual links (with href). Some other objects that should be links are links now too
• Metadata parses fields as dates when it shouldn't #208 time display issue
• refactor: directory structure #173 organize directory structure
• Remove vue-pdf dependency #156
• replace mdi library by svg-based treeshakeable library, reducing build size by ~3MB to, down to ~0.5MB gzipped
• improved layout of audio player, including marquee effect when the title does not fit in the screen
• cool random-but-persistent placeholder images for audio/video!

[femans]

(reply to @Szeket review):
to summarize:

• footer covers bottom results < the footer appears if you scroll up, even 1px is enough. it dissappears if you scroll down. If this is not the case, please let me know all the details. I have tried with the same browser and the same query as you did.
• Most files don't work in the audio player. Something to make an issue report out of, unless the behavior is different than previously
• NSFW-errors and nsfw classification not available - should be fixed

[dokterbob]

@femans I really would prefer not to have these code climate issues here. It doesn't imply we need to do what CodeClimate says, but I'd rather not get 71 issue notifications something isn't much alright.

Would it be possible for you to suggest some workaround (e.g. disable eslint in CodeClimate)?

[femans]

@femans I really would prefer not to have these code climate issues here. It doesn't imply we need to do what CodeClimate says, but I'd rather not get 71 issue notifications something isn't much alright.

Would it be possible for you to suggest some workaround (e.g. disable eslint in CodeClimate)?

@dokterbob couple of things; 1, I would rather not have 70 issues either, but if these are the same issue and the issue is nonsense, I will not stop this from deploying. 2, Great idea to remove the eslint check! I did this, but remember that we wil need to add to the CI pipeline npm run lint.