Provide QOS information of each cluster

[iparask]

Currently, the Campaign manager does not have knowledge of the possible queues and QOS of the selected cluster. As a consequence, we cannot automatically check if the campaign for execution fits in the cluster in total, or find a size that allows for the correct execution of the campaign.

Introducing policy awareness, allows one to make sure that the best case policy is selected for the campaign, given its deadline. Furthermore, we may want to break the campaign to multiple slurm submission so that the deadline is respected and achieved.

There are two main tasks: