Integrate gitlab-ci/yt-160-gitlab-ci-integration-often-fails-on-merge-yocto-step

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ff906931

YT-160: Workaround to prevent CI integration failure in 'merge-yocto' step

  The GitLab CI integration job frequently fails on the 'merge-yocto' step,
  specifically at the "git fetch" stage.
  The issue occurs because Git fails to fetch the .gitlab-ci submodule
  due to an incorrect reference, likely caused by the shallow clone
  (--depth=1) configuration, which limits the commit history.

  Extending the clone depth to --depth=2 helps prevent this error
  by providing a slightly deeper commit history,
  which resolves the reference issue.

.gitlab-ci @ ff906931

-Subproject commit f0ed0f4fd8cea2d0c76aabc102c68bf89fe96fbc
+Subproject commit ff906931bfb8018298518f539b73f4107abe7e7b

.gitlab-ci.yml

@@ -4,9 +4,9 @@
 # ---------------------------------------------------------------------------------------
 include:
   - project: '${CI_PROJECT_ROOT_NAMESPACE}/yocto/infrastructure/gitlab-ci'
-    ref: f0ed0f4fd8cea2d0c76aabc102c68bf89fe96fbc
+    ref: ff906931bfb8018298518f539b73f4107abe7e7b
     file: 'manifest-integration.yml'
 
 variables:
-  GITLAB_CI_REVISION: f0ed0f4fd8cea2d0c76aabc102c68bf89fe96fbc
+  GITLAB_CI_REVISION: ff906931bfb8018298518f539b73f4107abe7e7b
   BB_RECIPE_NAME: seco-yocto-testsuite