Use cached features in /rows
/rows needs the cached `features` since they're not always available in the parquet metadata.
This was causing some `Image` columns to be seen as a struct of binary data, which are not supported in the viewer (shown as "null").

Therefore I'm now passing the `features` from `config-parquet-and-info` to `config-parquet` and then to `config-parquet-metadata`. I kept it backward compatible in case a cached value doesn't have this field yet.

Therefore there's no need for a mongo migration. We can just re-run all the `config-parquet` and `config-parquet-metadata` jobs. I incremented their versions.

close https://github.com/huggingface/datasets-server/issues/1421
Use cached features in /rows: /rows needs the cached `features` since they're not always available in the parquet metadata.
This was causing some `Image` columns to be seen as a struct of binary data, which are not supported in the viewer (shown as "null").

Therefore I'm now passing the `features` from `config-parquet-and-info` to `config-parquet` and then to `config-parquet-metadata`. I kept it backward compatible in case a cached value doesn't have this field yet.

Therefore there's no need for a mongo migration. We can just re-run all the `config-parquet` and `config-parquet-metadata` jobs. I incremented their versions.

close https://github.com/huggingface/datasets-server/issues/1421