ci(k3d): guard k3d trigger jobs against recursion on stable branches
What does this MR do?
Fixes a latent k3d CI recursion bug. The k3d / k3d_arm64 jobs extend: .trigger_review_job, whose trigger.include re-includes the entire
.gitlab-ci.yml in a child pipeline and forwards PIPELINE_TYPE. Their
STABLE_BRANCH_PIPELINE rule was the only auto-run rule missing the
$CI_PIPELINE_SOURCE != "parent_pipeline" guard that the primary/manual rules
carry — so on a stable branch, the child pipeline (source parent_pipeline)
re-matched the rule and re-triggered the whole k3d matrix, spawning grandchild
pipelines recursively.
This is dormant on master (master pipelines are DEFAULT_BRANCH_PIPELINE,
and the k3d job has no unguarded default-branch rule) but active on the stable
branches that inherit this config — observed on 9-11-stable (e.g. pipeline →
child → grandchild k3d chains after a push).
Adds the parent_pipeline guard to the STABLE_BRANCH_PIPELINE rule on both
k3d and k3d_arm64. CI-only; the test jobs (review_specs_k3d / qa_k3d)
that must run inside the child are unaffected.
Related issues
Related to #6421 (closed)