Merge meilisearch#2366

2366: Bump milli to v0.26.4 r=curquiza a=curquiza

Fixes the milli related issues
- meilisearch#2352
- meilisearch#2358
- meilisearch#2338

Co-authored-by: Clémentine Urquizar <clementine@meilisearch.com>
Co-authored-by: Kerollmops <clement@meilisearch.com>

Merge meilisearch#2332

2332: fix(search): formatted field r=curquiza a=irevoire

fix meilisearch#2318

Co-authored-by: Irevoire <tamo@meilisearch.com>

Merge meilisearch#2321

2321: Bump milli r=curquiza a=irevoire



Co-authored-by: Irevoire <tamo@meilisearch.com>

Merge meilisearch#2178

2178: Refacto docker r=irevoire a=irevoire

closes meilisearch#2166 and meilisearch#2085

-----------

I noticed many people had issues with the default configuration of our Dockerfile.
Some examples:
- meilisearch#2166: If you use ubuntu and mount your `data.ms` in a volume (as shown in the [doc](https://docs.meilisearch.com/learn/getting_started/installation.html#download-and-launch)), you can't run meilisearch
- meilisearch#2085: Here, meilisearch was not able to erase the `data.ms` when loading a dump because it's the mount point
Currently, we don't show how to use the snapshot and dumps with docker in the documentation. And it's quite hard to do:
  - You either send a big command to meilisearch to change the dump-path, snapshot-path and db-path a single directory and then mount that one
  - Or you mount three volumes
- And there were other issues on the slack community

I think this PR solve the problem.
Now the image contains the `meilisearch` binary in the `/bin` directory, so it's easy to find and always in the `PATH`.
It creates a `data` directory and moves the working-dir in it.
So now you can find the `dumps`, `snapshots` and `data.ms` directory in `/data`.

Here is the new command to run meilisearch with a volume:
```
docker run -it --rm -v $PWD/meili_data:/data -p 7700:7700 getmeili/meilisearch:latest
```

And if you need to import a dump or a snapshot, you don't need to restart your container and mount another volume. You can directly hit the `POST /dumps` route and then run:
```
docker run -it --rm -v $PWD/meili_data:/data -p 7700:7700 getmeili/meilisearch:latest meilisearch --import-dump dumps/20220217-152115159.dump
```

-------

You can already try this PR with the following docker image:
```
getmeili/meilisearch:test-docker-v0.26.0
```

If you want to use the v0.25.2 I created another image;
```
getmeili/meilisearch:test-docker-v0.25.2
```

------

If you're using helm I created a branch [here](https://github.com/meilisearch/meilisearch-kubernetes/tree/test-docker-v0.26.0) that use the v0.26.0 image with the good volume 👍 
If you use this conf with the v0.25.2, it should also work.

Co-authored-by: Tamo <tamo@meilisearch.com>

Remove some useless indexer options

Expose indexer opts

Merge meilisearch#2246

2246: Release v0.26.1: bring "fix panic at start" commit (meilisearch#2243) into stable r=MarinPostma a=curquiza

2 commits
- cherry pick `32843f30d973349122ec5a37469ee09e6002b6f3` (merged in meilisearch#2243)
- change the version in the Cargo toml files (from v0.26.0 to v0.26.1)

Co-authored-by: ad hoc <postma.marin@protonmail.com>
Co-authored-by: Clémentine Urquizar <clementine@meilisearch.com>

Merge meilisearch#2209

2209: rename auto batching cli r=curquiza a=MarinPostma

rename `--enable-autobatching` to `--enable-auto-batching`.

as per meilisearch/specifications#96 (comment)

Co-authored-by: ad hoc <postma.marin@protonmail.com>

Merge meilisearch#2209

2209: rename auto batching cli r=curquiza a=MarinPostma

rename `--enable-autobatching` to `--enable-auto-batching`.

as per meilisearch/specifications#96 (comment)

Co-authored-by: ad hoc <postma.marin@protonmail.com>

Merge meilisearch#2200

2200: Fix(dumps): Explicitly define serde for time r=ManyTheFish a=ManyTheFish

fix meilisearch#2199 


Co-authored-by: ManyTheFish <many@meilisearch.com>