Consider support for further search engines on a scale between the existing two

[almereyda]

In continuation of #13, there is a feature gap between the two offered search engines, and a resource gap in what resources are needed for providing the desired functionality.

While the list of suggested alternatives was diverse and lacked a specific review in contrast to archivy's requirements, there are two outstanding (experimental, version < 1) examples that need to be mentionned again. They can be positioned right inbetween the two existing solutions:

• meilisearch (Rust)
  https://github.com/meilisearch/MeiliSearch
• typesense (C++)
  https://github.com/typesense/typesense

They should be able to combine the best of both worlds:

• written in performant languages
• feature complete (in comparison to RipGrep)
• comparatively low on resource consumtion (in comparison to ElasticSearch)

[Uzay-G]

I want to do this and appreciate you creating the issue, just have been very busy. If you'd be interested in working on this I could help you out with situation relevant code / writing too, otherwise i'd probably do this later in january or something.