Resolve "Downstream pipeline job that uses environments with approvals is not clickable" - pipeline mini graph

What does this MR do and why?

This MR resolves the issue where downstream pipeline jobs that use environments with approvals are not clickable. It's a similar change as in Resolve "Downstream pipeline job that uses envi... (!188806 - merged), but for the pipeline mini graph.

References

• #521308 (closed)
• !188806 (merged)

Screenshots or screen recordings

Before	After
Screen_Recording_2025-05-07_at_15.02.24	Screen_Recording_2025-05-07_at_14.23.00

How to set up and validate locally

1. Visit Project -> Environments and create an environment called production.
2. Visit Project -> Settings -> CI/CD -> protected environments and protect this environment.
3. Create an upstream pipeline config as follows:

stages:          # List of stages for jobs, and their order of execution
  - build
  - test
  - deploy

build-job:       # This job runs in the build stage, which runs first.
  stage: build
  script:
    - echo "Compiling the code..."
    - echo "Compile complete."

trigger_job:
  trigger:
    include:
      - local: child-pipeline.yml
  environment: production

4. Create the child pipeline config as follows:

downstream-job:       # This job runs in the build stage, which runs first.
  stage: test
  script:
    - echo "Compiling the code..."
    - echo "Compile complete."

5. Navigate to the pipelines list page and verify the trigger_job dropdown item. The job page is not available for the manual downstream job, and clicking the item should navigate to the deployment page from where the user can approve the deployment to proceed.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #521308 (closed)