ci-package-builder: Set --follow-tags only when needed

Rather surprisingly, `git push origin --follow-tags pristine-lfs-source`
ends up pushing the release tag as well.

Let's pass `--follow-tags` only when appropriate to avoid confusing
behaviors.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

ci-package-builder.yml

@@ -311,7 +311,7 @@ pull-mirror:
           # even if they're on the server.
           git config lfs.allowincompletepush true
           git lfs push --all ${CI_AUTH_PROJECT_URL} pristine-lfs
-          git push --follow-tags ${CI_AUTH_PROJECT_URL} pristine-lfs
+          git push ${CI_AUTH_PROJECT_URL} pristine-lfs
         else
           echo "No pristine-lfs; skipping"
         fi
@@ -547,7 +547,7 @@ build-source:
     # even if they're on the server.
     - git config lfs.allowincompletepush true
     - pristine-lfs -v import-dsc --full --branch "${PRISTINE_SOURCE}" "${DSC}"
-    - git push --follow-tags "${CI_AUTH_PROJECT_URL}" "${PRISTINE_SOURCE}:${PRISTINE_SOURCE}"
+    - git push "${CI_AUTH_PROJECT_URL}" "${PRISTINE_SOURCE}"
     - git push "${CI_AUTH_PROJECT_URL}" "${VERSIONTAG}"
     - echo "✨ Release pushed and tagged as ${VERSIONTAG}"
   artifacts: