Add linked pipelines to pipelines table

What does this MR do?

This MR adds linked pipelines (upstream/downstream) to the pipelines table component. This mimics the behavior used on the MR widget, which allows users to quickly navigate to an upstream or downstream pipeline. This change can be found when viewing the pipelines table or the pipelines tab on an MR (if your pipeline triggers another pipeline or has been triggered).

How to test (please test 😸)

Note: You need an active runner on your GDK that can pick up jobs.

Create a project named trigger-downstream or preference. Within that project have a .gitlab-ci.yml config. That project needs a job to trigger another pipeline in a project with a .gitlab-ci.yml config. This can be tested inverse with a project that gets triggered to create the upstream relationship.

The trigger job should look like

trigger_job:
  stage: test
  trigger: root/project_name

Related to: #36118 (closed)

Screenshots or Screencasts (strongly suggested)

LOCAL GDK

Pipelines Table

Pipelines Tab MR

Commit pipelines table

PRODUCTION CSS TEST IN BROWSER

These screenshots are to display no broken layout, does not include linked pipelines

Pipelines Table

Pipelines Tab MR

Commit pipelines table

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #36118 (closed)