Corpus query and text components

[MauPalantir]

This depends on https://github.com/acdh-oeaw/vicav-app-api/pull/1

[ctot-nondef]

components refactored to use composition API - untested d/t lack of menu points

[ctot-nondef]

@MauPalantir Thank you for these contributions! I ported your code to use Vues composition API, which we're trying to use throughout the project. This brings a couple of changes in how to set up reactivity etc but makes typing much easier and flexible.

A couple of points to implement:

• the API responses delivering structured data should ideally be typed and checked using zod - an example of this can be found in the mapData store that way our application won't break if corrupted data comes from the API and we'll always know right away by looking at the console
• when fetching data directly in the component, consider using the useAsyncData composable.the transform callback works nicely when performing the type checks.

[MauPalantir]

Implemented proper text loading and scrolling for UI. Left from feedback is the refactoring to use useAsyncData.

[ctot-nondef]

in order to merge this, we should replace the custom scss styling in corpus-text-window-content.vue with tailwind styling