Align CI and production environments
While investigating an issue (see https://github.com/huggingface/dataset-viewer/pull/2792#issuecomment-2110295795), I discovered that our CI and production environments are misaligned, and thus the CI does not strictly test what will happen in production.

For example, the `libsndfile1` package:
- CI uses `1.0.31` version
- Production uses `1.2.0` version

Another example, the `ffmpeg` package:
- CI uses `4.4.2` version
- Production uses `5.1.4` version

Also note that the Linux distributions are different:
- CI uses **Ubuntu**
  - It uses "ubuntu-latest", currently `ubuntu-22.04`
- Production uses **Debian**
  - Currently, it uses `python:3.9.18-slim` (EDIT: ~~`docker.io/nginx:1.25.3`~~) image, from `debian:12-slim` (bookworm)

We should align CI and production environments.
Align CI and production environments: While investigating an issue (see https://github.com/huggingface/dataset-viewer/pull/2792#issuecomment-2110295795), I discovered that our CI and production environments are misaligned, and thus the CI does not strictly test what will happen in production.

For example, the `libsndfile1` package:
- CI uses `1.0.31` version
- Production uses `1.2.0` version

Another example, the `ffmpeg` package:
- CI uses `4.4.2` version
- Production uses `5.1.4` version

Also note that the Linux distributions are different:
- CI uses **Ubuntu**
  - It uses "ubuntu-latest", currently `ubuntu-22.04`
- Production uses **Debian**
  - Currently, it uses `python:3.9.18-slim` (EDIT: ~~`docker.io/nginx:1.25.3`~~) image, from `debian:12-slim` (bookworm)

We should align CI and production environments.