Earlier branch: Ensure the verify_stable_branch job point out to security paths

Context

Before tagging the final release candidate, the stable branches from all GitLab managed components projects are automatically reviewed by the monthly_release_final_rc:verify_stable_branch job to ensure they're ready (green).

Since the security repositories are the SSOT of stable branches, #21349 (closed) adjusted the stable branch paths to use the security ones, instead of canonical. However, the logs are still pointing to the canonical paths:

https://ops.gitlab.net/gitlab-org/release/tools/-/jobs/19859974

❌ The following branches do not have green pipelines:
- cng-ee - 18-3-stable - running: https://gitlab.com/gitlab-org/build/CNG/-/commits/18-3-stable
- gitaly - 18-3-stable - failed: https://gitlab.com/gitlab-org/gitaly/-/commits/18-3-stable
- gitlab-ee - 18-3-stable-ee - running: https://gitlab.com/gitlab-org/gitlab/-/commits/18-3-stable-ee
- gitlab-pages - 18-3-stable - failed: https://gitlab.com/gitlab-org/gitlab-pages/-/commits/18-3-stable
- omnibus-gitlab-ee - 18-3-stable - running: https://gitlab.com/gitlab-org/omnibus-gitlab/-/commits/18-3-stable
- gitlab-ce - 18-3-stable - running: https://gitlab.com/gitlab-org/gitlab-foss/-/commits/18-3-stable

Problem

This led to confusion among release managers, as the canonical paths were green, but the security ones were not. The error logs should be adjusted to use the security path