Support for the blocking SvcQC.Dep criterion

[orviz]

The first and blocking criterion for the support of the service deployment is the SvcQC.Dep. This criterion will be added to the tooling JSON so that it can be automatically loaded by the web.

To support this criterion the web needs to:

• [ ] Implement the logic to make the SvcQC.Dep criterion as the requirement before selecting any other SvcQC-releated criteria
• [ ] Separate software criteria (QC.) from service (SvcQC.) criteria
• [ ] Load the configuration files for the deployment (such as k8s YAMLs). As a first step this could be narrowed down to files that must exist in a code repository, and thus, no support for loading files from local disk. However the repos must be available for running the pipeline, following the same approach as the code i.e. either defined in step 1 (Repos) or provide it at the last step before running the pipeline.

[orviz]

2 service-related criteria (SvcQC.Dep and SvcQC.Fun) are now avaliable in API staging (tooling version 1.5.0-alpha).

This enables the testing of the requirement that SvcQC.Dep shall go first, blocking the rest of service-related criteria