PMG job updates Part 1 - Update legacy pipeline mini graph upstream/downstream

What does this MR do and why?

Part 1 of #384853

We are re-routing the legacy-pipeline-mini-graph (which is all 3 pipeline tables) to use GraphQL after the initial render. This will ultimately keep all dropdowns etc up to date whether the PMG is in a widget or a table. This also sets us up to implement downstream job visualization.

In part 2, we will re-route pipeline stages to the GraphQL component and remove the child components of <legacy-pipeline-mini-graph>

Screenshots or screen recordings

No UI change. This is what upstream/downstreams look like

How to set up and validate locally

In a project with pipelines, make sure the pipeline mini graph upstreams/downstreams render in the following tables:

• Build > Pipelines
• Commit page > Pipelines tab
• MR page > Pipelines tab

To create an upstream

in a test project, navigate to "Build > Pipeline editor" and add the following to `.gitlab-ci.yml`

upstream:
  trigger:
    project: flightjs/project-b

Navigate to flightjs/project-b and your upstream should appear

To create a downstream

in a test project, navigate to "Build > Pipeline editor" and add the following to `.gitlab-ci.yml`

bridge_job:
  stage: build
  trigger:
    include: test.yml

If you do not have a file called test.yml, the downstream should fail. The important part is that it renders