v1.45.0

Meilisearch v1.45.0 mainly improves indexing performance when changing settings and also improves document fetch performance.

### ✨ Enhancement

- **Autobatch deletions by filter with additions** by @Kerollmops in https://github.com/meilisearch/meilisearch/pull/6389
   While Meilisearch tries to improve indexing speed when users add documents and mix those additions with deletions via a filter, it is still an anti-pattern to interleave both. It is recommended to delete documents by ID whenever possible, as the engine is optimized to merge them, thereby drastically speeding up indexation.
- **Improve settings indexing performance & visibility**
   We are introducing support for more settings in the nez settings indexer. If you find any bugs, please report them on GitHub. You can disable the new settings indexer by setting the environment variable like this: `MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_SETTINGS=true` or use the equivalent dedicated CLI parameter.
    - **Support non-extracting parameters** by @Kerollmops in https://github.com/meilisearch/meilisearch/pull/6393
      Changing one of the following settings is now directly handled by the new settings indexer: displayed fields, synonyms, the primary key, authorize typos, min word len one and two typos, max values per facet, sort facet values by, pagination max total hits, search cut off, chat, and foreign keys.
    - **Support the global facet search** by @Kerollmops in https://github.com/meilisearch/meilisearch/pull/6390
       Meilisearch can use the new settings indexer when the settings change the facet search root boolean parameter.

### 🪲 Bug Fixes

- **Fetching documents no longer blocks the actix worker** @dureuill in https://github.com/meilisearch/meilisearch/pull/6402
- **Fix an internal error when changing the binary quantization** by @Kerollmops in https://github.com/meilisearch/meilisearch/pull/6396
   We fixed an issue where users were changing the binary-quantized boolean in embedder configurations. The change corrupted the database, making it impossible to change the quantization in the future. Users had to create a binary-quantized embedder from scratch, or they could never change it again.
        
### 🔩 Miscellaneous

- Make timeout test less flaky on Windows by @dureuill in https://github.com/meilisearch/meilisearch/pull/6388

**Full Changelog**: https://github.com/meilisearch/meilisearch/compare/v1.44.0...v1.45.0