pull-updates: check CI_COMMIT_BRANCH for passing --backports or --proposed-updates to apertis-pkg-pull-updates

pull-updates: check CI_COMMIT_BRANCH for passing --backports or --proposed-updates to apertis-pkg-pull-updates

Previously, apertis-pkg-pull-updates pulled by default versions from backports or proposed-updates repositories. Since it was more confusing than heplful because not part of our usual workflow, these repo are now optional. This change allows to control which repo needs to be checked by running the job on a 'debian/-backports' or 'debian/-proposed-updates' branch.

Depends on pkg/apertis-dev-tools!67 (merged)

https://phabricator.apertis.org/T9538

ci-package-builder.yml

@@ -396,11 +396,22 @@ pull-updates:
     - PULL_RELEASE_VENDOR=${PULL_RELEASE_BRANCH%%/*} # debian/buster → debian
     - PULL_RELEASE_NAME=${PULL_RELEASE_BRANCH##*/} # debian/buster → buster
     - echo "Pull $PACKAGE updates from $PULL_RELEASE_VENDOR $PULL_RELEASE_NAME"
+    - |
+      if [[ "$CI_COMMIT_BRANCH" == debian/*-backports ]]; then
+        ADDREPO=--backports
+        echo "Checking backports repository"
+      elif [[ "$CI_COMMIT_BRANCH" == debian/*-proposed-updates ]]; then
+        ADDREPO=--proposed-updates
+        echo "Checking proposed-updates repository"
+      else
+        ADDREPO=""
+      fi
     - set -x;
       apertis-pkg-pull-updates
         --package=${PACKAGE}
         --upstream=${PULL_RELEASE_NAME}
-        --mirror=${DEBIAN_MIRROR};
+        --mirror=${DEBIAN_MIRROR}
+        ${ADDREPO};
       set +x
     # Avoid pack-objects running out of memory on bigger repositories
     - git config pack.windowMemory 512m