Delete and get documents by filter

[dureuill]

Product card (internal only): https://www.notion.so/meilisearch/Enhance-document-management-Get-Delete-by-filter-999adc1dc73c4a5381f0b84e523ad3be
Related product discussion: meilisearch/product#284
Related specifications:

• Get documents by filter: Specify the new fetch documents route specifications#234
• Delete documents by filter: Get and delete documents by filter specifications#236

Implemented in:

• Get documents by filter: Get documents by filter #3570
• Delete documents by filter: Delete documents by filter #3550

Impacted teams

@meilisearch/docs-team
@meilisearch/integration-team

[curquiza]

For people following this issue: we probably will not be able to make it for v1.1. In this case, this improvement will be implemented for v1.2 😇

[curquiza]

Officially not ready for v1.1 (as expected) to focus on other priorities 😊
Reported to v1.2 💪

[dureuill]

Opened #3550 as an initial exploration of the feature.

This surfaces a few product questions.

1. Should we reuse the existing /indexes/{:indexUid}/documents/delete-batch route, or use a new one (e.g. ../delete-filter)?
2. Similarly, should we reuse the existing documentDeletion task type, or introduce a new documentDeletionByFilter task type?
3. What should be the "details" of the task when performing a delete by filter?
4. If reusing the documentDeletion task, what should we do of the providedIds field? Should it be set to null, absent altogether, ...?
5. Should the filter be applied on the documents as they are in the index when the query is received ("query time"), or as they are once all the previously sent updates have been asynchronously applied by the scheduler ("processing time")? Whichever solution we choose, I think the documentation should talk about this timing issue and discourage the use of "flaky" filters that are too dependent on an update being applied or not to the document (for instance, filters on fields that are often updated).