Disable dataset scripts
The `config-parquet-and-info` step will now raise a `DatasetWithScriptNotSupportedError` for datasets with a script, except those in the allow list. This will prevent users from running arbitrary code using dataset scripts.

The error message is shown to the user on the website and it says
```python
            raise DatasetWithScriptNotSupportedError(
                "The dataset viewer doesn't support this dataset because it runs "
                "arbitrary python code. Please open a discussion in the discussion tab "
                "if you think this is an error and tag @lhoestq and @severo."
            )
```

The allow list is hardcoded for now: `DATASET_SCRIPTS_ALLOW_LIST = ["canonical"]`
The keyword "canonical" means all the datasets without namespaces.

We can add other datasets to the allow list, and it supports `fnmatch`, for example to support all the datasets from `huggingface` we can add `huggingface/*` to the allow list.

cc @severo @XciD 
Disable dataset scripts: The `config-parquet-and-info` step will now raise a `DatasetWithScriptNotSupportedError` for datasets with a script, except those in the allow list. This will prevent users from running arbitrary code using dataset scripts.

The error message is shown to the user on the website and it says
```python
            raise DatasetWithScriptNotSupportedError(
                "The dataset viewer doesn't support this dataset because it runs "
                "arbitrary python code. Please open a discussion in the discussion tab "
                "if you think this is an error and tag @lhoestq and @severo."
            )
```

The allow list is hardcoded for now: `DATASET_SCRIPTS_ALLOW_LIST = ["canonical"]`
The keyword "canonical" means all the datasets without namespaces.

We can add other datasets to the allow list, and it supports `fnmatch`, for example to support all the datasets from `huggingface` we can add `huggingface/*` to the allow list.

cc @severo @XciD 