[9.x] Handle non-consecutive key collection on MeiliSearch document deletion

[pyrou]

Methods MeiliSearchEngine::update() and MeiliSearchEngine::delete() both expect a Illuminate\Database\Eloquent\Collection of models.

For my use case I used to fine-tune this collection using ->filter() on it. Using ->filter() on collection might result in a collection that doesn't wrap a list anymore, but an array with non-consecutive keys. While MeiliSearchEngine::update() implementation handle this well, calling the MeiliSearchEngine::delete() method results in following error from Meilisearch:

Meilisearch ApiException: Http Status: 400 - Message: Json deserialize error: invalid type: map, expected a sequence at line 1 column 0 - Code: bad_request - Type: invalid_request - Link: https://docs.meilisearch.com/errors#bad_request

This is because delete() method uses ->all() directly on the provided Collection.

You might argue I should use ->values() in my user-land code, and this is what I did for the moment as a workaround. But IMHO, update() and delete() should behave the same with array that are not list.

This PR propose to change ->all() to ->values()->all().

[mmachatschek]

This should be updated on the Algolia driver as well I guess as that driver shares the same logic

[driesvints]

@pyrou can you PR to AlgoliaEngine as well?

[pyrou]

@driesvints AlgoliaEngine doesn't suffer from same "issue".
If we follow the AlgoliaEngine code (deleteObjects, splitIntoBatches), model collection passed is used in a foreach that doesn't use keys.