Config-level parquet-and-dataset-info
Will solve https://github.com/huggingface/datasets-server/issues/866

Part of https://github.com/huggingface/datasets-server/issues/735

# Questions:
* Didn't I miss anything? 
* Should there be any migration jobs? Technically it's a new job runner, it's not equal to the previous dataset-level one (results are not identical), and the old one doesn't exist anymore. 
* Can I rename relevant environmental variables (like `PARQUET_AND_DATASET_INFO_BLOCKED_DATASETS` -> to `PARQUET_AND_INFO_BLOCKED_DATASETS`) or might it break anything?  

Config-level parquet-and-dataset-info: Will solve https://github.com/huggingface/datasets-server/issues/866

Part of https://github.com/huggingface/datasets-server/issues/735

# Questions:
* Didn't I miss anything? 
* Should there be any migration jobs? Technically it's a new job runner, it's not equal to the previous dataset-level one (results are not identical), and the old one doesn't exist anymore. 
* Can I rename relevant environmental variables (like `PARQUET_AND_DATASET_INFO_BLOCKED_DATASETS` -> to `PARQUET_AND_INFO_BLOCKED_DATASETS`) or might it break anything?  
