This PR support for pre-filtering in storage backends
closes: #263

TODOs:

• modify the interface of find and add parameter filter, by default None. Handle the following cases:

  • If filter is not None and query is vector => perform filtered vector search if supported otherwise raise error (backend raises an error).
    • Needs test of raised error
  • If filter is not None and query is None => perform filter operation (exhaustive filtering if efficient backend filter is not supported otherwise, use filter from backend).
  • If query is a dict and filter is None, perform a filter operation (to preserve compatibility).
  • If filter is not None and and query is not None or vector, raise error.

• use pre-filtering in _find:

  • use pre-filtering in _find for weviate
  • use pre-filtering in _find for qdrant
  • use pre-filtering in _find for annlite

• define the schema of tags in config for both annlite, weaivate and qdrant:

  • Schema is based on columns which is part of QdrantConfig, AnnliteConfig, ElasticSearchConfig, SqliteConfig
  • schema for annlite
  • schema for weaviate
  • schema for qdrant

• modify set_doc_by_id and make sure to include tags specified in the schema definition

  • set_doc_by_id for annlite
  • set_doc_by_id for weaviate
  • set_doc_by_id for qdrant
  • same for set_docs_by_ids if implemented in the backend

• Documentation for

  • annlite
  • weaviate
  • qdrant

• Tests that leverage pre-filtering for

  • annlite
  • weaviate
  • qdrant