Use local storage (NVMe) instead of EFS volumes
The worker machines have NVMe, and we should use this local storage instead of EFS for:
- stats cache
- HF datasets cache
- duckdb index cache

We still need to use EFS for parquet metadata since it's shared data, and for duckdb local cache in `services/search`.

Note that `services/admin` and `clean-...`  cron jobs access the same EFS volumes, but it's respectively to: 1. provide metrics on EFS storage, and 2. clean the old files.

Once fixed, `admin` will only mount and report on the usage of the parquet-metadata and duckdb volumes, and the `clean-...` cron jobs for the deleted EFS volumes will be deleted.

For NVMe: we have to ensure that the worker app has the right to create the directories. We could use /tmp as it's always writable, contrarily to the root, and it's on the same disk:

```
I have no name!@prod-datasets-server-worker-medium-5889fdfc4-4f624:/src/services/worker$ df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
overlay         885G   14G  871G   2% /

I have no name!@prod-datasets-server-worker-medium-5889fdfc4-4f624:/src/services/worker$ ls -al /tmp
total 324
drwxrwxrwt 1 root root      48 Mar  8 16:57 .

I have no name!@prod-datasets-server-worker-medium-5889fdfc4-4f624:/src/services/worker$ ls -al /
total 0
drwxr-xr-x   1 root root  54 Mar  8 16:57 .
```
Use local storage (NVMe) instead of EFS volumes: The worker machines have NVMe, and we should use this local storage instead of EFS for:
- stats cache
- HF datasets cache
- duckdb index cache

We still need to use EFS for parquet metadata since it's shared data, and for duckdb local cache in `services/search`.

Note that `services/admin` and `clean-...`  cron jobs access the same EFS volumes, but it's respectively to: 1. provide metrics on EFS storage, and 2. clean the old files.

Once fixed, `admin` will only mount and report on the usage of the parquet-metadata and duckdb volumes, and the `clean-...` cron jobs for the deleted EFS volumes will be deleted.

For NVMe: we have to ensure that the worker app has the right to create the directories. We could use /tmp as it's always writable, contrarily to the root, and it's on the same disk:

```
I have no name!@prod-datasets-server-worker-medium-5889fdfc4-4f624:/src/services/worker$ df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
overlay         885G   14G  871G   2% /

I have no name!@prod-datasets-server-worker-medium-5889fdfc4-4f624:/src/services/worker$ ls -al /tmp
total 324
drwxrwxrwt 1 root root      48 Mar  8 16:57 .

I have no name!@prod-datasets-server-worker-medium-5889fdfc4-4f624:/src/services/worker$ ls -al /
total 0
drwxr-xr-x   1 root root  54 Mar  8 16:57 .
```