sim search refactoring

[fynnos]

This PR refactors the sim search service by splitting the functionality into multiple services:

Old: simsearch service is basically hard-wired to use weaviate

new: simsearch service provides generic methods to search for similar images, sentences, documents etc. it internally uses a vectorIndexService (via interface/abstract class)
to retain the old behavior, there is an implementation of the vectorindexService using weaviate. However, I've also included some partial implementations to try out typesense and qdrant instead.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11487172	Triggered	Company Email Password	1a484f5	docker/.env.example	View secret
11487172	Triggered	Company Email Password	d23c72c	docker/.env.example	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[bigabig]

puh. mit 3 vector dbs müssen einige neue configs in .env.example(s) eingeführt werden.

das depends_on in compose.yml wird ein echtes problem. bin gespannt ob das gelöst werden kann, ob man die irgendwie dynamisch machen kann