Update meilisearch stub to reflect new data path

[tdondich]

Meilisearch, since v0.27 has updated their working data path to /meili_data. See: https://blog.meilisearch.com/whats-new-in-v0-27/

This fix resolves persistence with images that come after v0.27, including 'latest', which sail uses.

[AlejandroAkbal]

Thanks for fixing it, hope it is merged soon!

[bram-pkg]

Isn't this the second time in a relatively short time, that this has been changed 🤔

[tdondich]

I think it’s the price we pay if we utilize the latest tag vs a fixed image tag version. If we utilize a fixed image tag version for this and other images used then we avoid this problem and we can update the versions during sail package version updates with an upgrade guide. Just my two cents. I love sail!

[bram-pkg]

I do agree Sail should use latest tags. It's just a tad annoying that Meilisearch keeps changing it's mind about where to store data :)

[tdondich]

I actually think we should fix the image versions to set versions along with each sail release. We do it for mysql and pgsql and others but not for packages like mailhog or meilisearch or selenium. Basically sails expectations may break if one of the dependencies introduce a breaking change in their latest tag. Latest may introduce a major version change just like this one. This change was introduced in a major version update. Shame dockerhub tags don’t simulate semver to better handle this.