Make fetching of backports and proposed-updates repositories optional

The Apertis pipeline imports backport and/or proposed-updates versions by default, this is not needed and leads to miss some security updates. Because, importing versions from backports and proposed-updates is not part of our standard workflow, this should only be optional to avoid confusing the pipeline.

See infrastructure/ci-package-builder!316 (merged) for the ci-package-builder part.

https://phabricator.apertis.org/T9538

debian/changelog

+apertis-dev-tools (0.2023.11) apertis; urgency=medium
+
+  * apertis-pkg-pull-updates: Make fetching of backports and proposed-updates
+    repositories optional.
+    The Apertis pipeline imports backport and/or proposed-updates versions
+    by default, this is not needed and leads to miss some security updates.
+    Because, importing versions from backports and proposed-updates is not
+    part of our standard workflow, this should only be optional to avoid
+    confusing the pipeline.
+  * apertis-pkg-pull-updates: pull updates from *-updates repositories
+    Updates from *-proposed-updates repositories are not pulled anymore
+    by default because it can contain undesirable updates for Apertis.
+    "proposed-updates" contains updates not officialy part of Debian
+    contrary to "updates".
+    However, we still want updates from *-updates repositories instead.
+
+ -- Dylan Aïssi <daissi@debian.org>  Mon, 15 Jan 2024 10:14:54 +0100
+
 apertis-dev-tools (0.2023.10) apertis; urgency=medium
 
   * import-debian-package: avoid oversized commit messages