Bleeding edge release jobs should not run for community contribution merge requests

Problem

The bleeding edge release jobs (docker images, S3, packagecloud, pulp) are currently running when a GitLab team member triggers a pipeline on a community contribution merge request

They should NOT run when testing a community contribution from a fork.

Note: In the related MR, the Community contribution was on the feature/build-pod-resource branch

Likely Root Cause

The .rules:release:bleeding-edge rule in .gitlab/ci/_rules.gitlab-ci.yml includes the condition:

- <<: *if-runner-or-security-runner-feature-ref changes: *code-backstage-patterns

This condition matches any feature/* branch in the canonical projects, but doesn't account for merge requests from community forks. When a team member triggers a pipeline on a community MR, it runs in the context of the canonical project, causing the bleeding edge jobs to execute.

Related Issue

Discovered in !5922 (merged)