Create Qdrant payload field indexes (keyword, integer, float, bool, datetime, uuid, full-text, geo) with correct tokenizer and on-disk settings

Documented steps

1. Simple index: PUT /collections/{collection_name}/index with {"field_name":"city","field_schema":"keyword"}. Supported simple schemas: keyword, integer, float, bool, geo, datetime, uuid.
2. Use field_schema "uuid" for UUID-formatted string fields instead of "keyword" — a more memory-efficient keyword-like index (v1.11.0+).
3. Use "bool" to enable Match filtering on boolean fields (v1.4.0+) and "datetime" to enable Range filtering on RFC 3339 timestamps (v1.8.0+).
4. Tune integer indexes with the parameterized form: {"field_name":"age","field_schema":{"type":"integer","lookup":false,"range":true}} to build only the access patterns you need (v1.8.0+).
5. Full-text index: {"field_name":"description","field_schema":{"type":"text","tokenizer":"word","min_token_len":2,"max_token_len":10,"lowercase":true}}. Tokenizers: word (default), whitespace, prefix (autocomplete), multilingual (CJK and other non-space-delimited languages).
6. Optional full-text tuning: "lowercase":false for case-sensitive matching, "ascii_folding":true to normalize accents (v1.16.0+), a Snowball "stemmer", language-based or custom "stopwords", and "phrase_matching":true for exact-phrase queries.
7. Move any index type to disk with {"field_schema":{"type":"keyword","on_disk":true}} (v1.11.0+) to trade RAM for disk I/O.
8. Suppress extra filter-aware HNSW edges on a high-cardinality field with {"field_schema":{"type":"keyword","enable_hnsw":false}} (v1.17.0+).
9. Drop an index: DELETE /collections/{collection_name}/index/{field_name}.
10. Reference: https://qdrant.tech/documentation/manage-data/indexing/