Prevent bleeding-edge jobs from running on CC

Community contribution branches may include `feature/` jobs, which
incorrectly triggers bleeding-edge workflows. This change ensures those
jobs are not executed on CC branches.

Author: Touni Atchadé

.gitlab/ci/_rules.gitlab-ci.yml

@@ -99,6 +99,9 @@
 .if-runner-or-security-bleeding-edge-release-ref: &if-runner-or-security-bleeding-edge-release-ref
   if: $CI_COMMIT_REF_NAME =~ /\Av[0-9]+\.[0-9]+\.[0-9]+-rc[0-9]+\z/ && ($CI_PROJECT_PATH == "gitlab-org/gitlab-runner" || $CI_PROJECT_PATH == "gitlab-org/security/gitlab-runner")
 
+.if-not-gitlab-runner-community-path: &if-not-gitlab-runner-community-path
+  if: $CI_MERGE_REQUEST_SOURCE_PROJECT_PATH != null && $CI_MERGE_REQUEST_SOURCE_PROJECT_PATH !~ /^gitlab-org($|\/)/
+
 ########################
 # Default branch rules #
 ########################
@@ -285,6 +288,8 @@
 
 .rules:release:bleeding-edge:
   rules:
+    - <<: *if-not-gitlab-runner-community-path
+      when: never
     - <<: *if-runner-default-branch
       changes: *code-backstage-patterns
     - <<: *if-runner-bleeding-edge-release-ref
@@ -296,6 +301,8 @@
 
 .rules:release-or-security:bleeding-edge-or-stable:
   rules:
+    - <<: *if-not-gitlab-runner-community-path
+      when: never
     - <<: *if-runner-or-security-runner-default-branch
       changes: *code-backstage-patterns
     - <<: *if-runner-or-security-bleeding-edge-release-ref