Update duckdb to 0.10.0
Will fix https://github.com/huggingface/datasets-server/issues/2413

This PR will include the following changes:
- Add a new job runner that will compute duckdb files with `0.10.0` -> Temporal cache kind `split-duckdb-index-010`
- Still have the old job runner that will compute duckdb files with `0.8.1` (Will use duckdb CLI to support two different duckdb versions, it was not possible with poetry) -> Cache kind is still split-duckdb-index to allow /search and /filter service working as usual while `split-duckdb-index-010` is being computed
- Will point the new job runner  `split-duckdb-index-010` to `/refs/convert/duckdb` instead or `refs/conver/parquet`
- Will add a new field in `split-duckdb-index-010` to specify the duckdb version used
- CLI [duckdb-081](https://github.com/duckdb/duckdb/releases/download/v0.8.1/duckdb_cli-linux-amd64.zip) is downloaded and unzipped in the docker container. 

Deploy plan - Once this PR is merged, deployed,  and all `split-duckdb-index-010` entries have been computed, send another PR to:
- Migration to delete all previous `split-duckdb-index` cache entries
- Migration to rename all cache entries with kind `split-duckdb-index-010` to `split-duckdb-index`
- Update the duckdb version in `/search` service
- Remove old code (I put TODOs to quickly identify which parts need to be removed from the old job runner)
- Refresh all entries for config-duckdb-index-size, split-is-valid, dataset-duckdb-index-size, config-is-valid, dataset-is-valid, dataset-hub-cache (Maybe increase job runner version and backfill?)
- Stop workers when deploying
Update duckdb to 0.10.0: Will fix https://github.com/huggingface/datasets-server/issues/2413

This PR will include the following changes:
- Add a new job runner that will compute duckdb files with `0.10.0` -> Temporal cache kind `split-duckdb-index-010`
- Still have the old job runner that will compute duckdb files with `0.8.1` (Will use duckdb CLI to support two different duckdb versions, it was not possible with poetry) -> Cache kind is still split-duckdb-index to allow /search and /filter service working as usual while `split-duckdb-index-010` is being computed
- Will point the new job runner  `split-duckdb-index-010` to `/refs/convert/duckdb` instead or `refs/conver/parquet`
- Will add a new field in `split-duckdb-index-010` to specify the duckdb version used
- CLI [duckdb-081](https://github.com/duckdb/duckdb/releases/download/v0.8.1/duckdb_cli-linux-amd64.zip) is downloaded and unzipped in the docker container. 

Deploy plan - Once this PR is merged, deployed,  and all `split-duckdb-index-010` entries have been computed, send another PR to:
- Migration to delete all previous `split-duckdb-index` cache entries
- Migration to rename all cache entries with kind `split-duckdb-index-010` to `split-duckdb-index`
- Update the duckdb version in `/search` service
- Remove old code (I put TODOs to quickly identify which parts need to be removed from the old job runner)
- Refresh all entries for config-duckdb-index-size, split-is-valid, dataset-duckdb-index-size, config-is-valid, dataset-is-valid, dataset-hub-cache (Maybe increase job runner version and backfill?)
- Stop workers when deploying