Improve selection of the next job to priorize datasets with few configs/splits
Internal Slack conversation: https://huggingface.slack.com/archives/C04L6P8KNQ5/p1698323643019099?thread_ts=1698323528.797149&cid=C04L6P8KNQ5

> `opus_euconst` is squatting the pods, and the small datasets are waiting for too long before being processed.
![image](https://github.com/huggingface/datasets-server/assets/1676121/976df781-fda8-4072-9133-9a2cdd273eb6)
> maybe switch it to "low" prior ?
> It could be a good solution for these big datasets, indeed! If number of configs or splits is over some threshold -> change the priority to low.
> I like it, because it would not change our bottleneck query, which is to find the next job to process.


Improve selection of the next job to priorize datasets with few configs/splits: Internal Slack conversation: https://huggingface.slack.com/archives/C04L6P8KNQ5/p1698323643019099?thread_ts=1698323528.797149&cid=C04L6P8KNQ5

> `opus_euconst` is squatting the pods, and the small datasets are waiting for too long before being processed.
![image](https://github.com/huggingface/datasets-server/assets/1676121/976df781-fda8-4072-9133-9a2cdd273eb6)
> maybe switch it to "low" prior ?
> It could be a good solution for these big datasets, indeed! If number of configs or splits is over some threshold -> change the priority to low.
> I like it, because it would not change our bottleneck query, which is to find the next job to process.

