add cacheable ParquetResponseEmptyError in first-rows-from-parquet
Part of https://github.com/huggingface/datasets-server/issues/1443
Currently, we have `{ _id: { cause: 'ParquetResponseEmptyError' }, count: 303 }`, records in cache collection with UnexpectedError because of `ParquetResponseEmptyError`.
Actually, we have two definitions of `ParquetResponseEmptyError`: one in parquet_utils.py https://github.com/huggingface/datasets-server/blob/main/libs/libcommon/src/libcommon/parquet_utils.py#L29 and another in https://github.com/huggingface/datasets-server/blob/main/libs/libcommon/src/libcommon/exceptions.py#L424.
`SplitFirstRowsFromParquetJobRunner` should throw the cacheable version of `ParquetResponseEmptyError` but currently it is not handling the noncacheable exception leading to an `UnexpectedError`.
After this PR, I will refresh the cache of the 303 records.

add cacheable ParquetResponseEmptyError in first-rows-from-parquet: Part of https://github.com/huggingface/datasets-server/issues/1443
Currently, we have `{ _id: { cause: 'ParquetResponseEmptyError' }, count: 303 }`, records in cache collection with UnexpectedError because of `ParquetResponseEmptyError`.
Actually, we have two definitions of `ParquetResponseEmptyError`: one in parquet_utils.py https://github.com/huggingface/datasets-server/blob/main/libs/libcommon/src/libcommon/parquet_utils.py#L29 and another in https://github.com/huggingface/datasets-server/blob/main/libs/libcommon/src/libcommon/exceptions.py#L424.
`SplitFirstRowsFromParquetJobRunner` should throw the cacheable version of `ParquetResponseEmptyError` but currently it is not handling the noncacheable exception leading to an `UnexpectedError`.
After this PR, I will refresh the cache of the 303 records.
