gitlab: fix republishing containers after forced pipeline

Currently containers are only published in response to a 'push' event
which touched the container sources.

If we need to recover from pristine state with no containers, then we
must publish containers if a pipeline is forced with 'RUN_PIPELINE=1'
on the default branch too.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

.gitlab-ci.yml

@@ -43,8 +43,8 @@ stages:
     - docker login registry.gitlab.com -u ${CI_REGISTRY_USER} -p ${CI_REGISTRY_PASSWORD}
   script:
     - docker build --tag ${CI_REGISTRY_IMAGE}/${NAME}:latest containers/${NAME}
-    - if test "${CI_PIPELINE_SOURCE}" = "push" &&
-         test "${CI_COMMIT_REF_NAME}" = "${CI_DEFAULT_BRANCH}";
+    - if test "${CI_COMMIT_REF_NAME}" = "${CI_DEFAULT_BRANCH}" &&
+         ( test "${CI_PIPELINE_SOURCE}" = "push" || test "${RUN_PIPELINE}" = "1" )
       then
           docker push ${CI_REGISTRY_IMAGE}/${NAME}:latest;
       fi