ci: Define the integration job tag dynamically via a variable
ci: Define the integration job tag dynamically via a variable

Custom runners are private to a project, so naturally forks cannot run
any workloads on these. The integration test suite which requires
access to our custom runner is naturally disabled on forks and can be
enabled by setting LIBVIRT_CI_INTEGRATION=1.
The problem is that the current integration jobs definitions have tags
statically defined as 'redhat-vm-host'. If users are going to supply
their own private runners for their forks, they can define whatever
tags they want with it and so unless they add 'redhat-vm-host' to their
own runner's tags, the pipeline won't run.
To solve this, define the integration job tag using a variable. The
repo config will use the value defined in the job for the variable
while users can override the value easily on a project/pipeline level
thanks to GitLab's CI variable precedence [1].

[1] https://docs.gitlab.com/ee/ci/variables/#cicd-variable-precedence

Signed-off-by: Erik Skultety <2c14d38fa47c8799f1b9c16280abe27f8edfec6e@redhat.com>
Reviewed-by: Michal Privoznik <83d82aaba2eed257f4814b0c239c260c4caaadf0@redhat.com>

olafhering/libvirt,jfehlig/libvirt,olafhering/libvirt,jfehlig/libvirt,libvirt/libvirt,olafhering/libvirt,jfehlig/libvirt,zippy2/libvirt,crobinso/libvirt,olafhering/libvirt,libvirt/libvirt,libvirt/libvirt,crobinso/libvirt,crobinso/libvirt,zippy2/libvirt,zippy2/libvirt,libvirt/libvirt,jfehlig/libvirt,zippy2/libvirt,crobinso/libvirt