Refactor logic to display forked badges for pipelines
What does this MR do and why?
The current logic for displaying if a pipeline is from a fork is very bug prone. It's surfaced hard to replicate help requests like https://gitlab.com/gitlab-com/ops-sub-department/section-ops-request-for-help/-/issues/438
We are refactoring the business logic on the client and using a BE data source directly to determine if a pipeline is from a fork or not. Which in return should make the code more reliable.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Forked
Not forked
Query Plans
Here are the query plans for the taken changes:
Before: https://postgres.ai/console/gitlab/gitlab-production-main/sessions/32629/commands/100705 https://postgres.ai/console/gitlab/gitlab-production-main/sessions/32629/commands/100708
After: https://postgres.ai/console/gitlab/gitlab-production-main/sessions/32629/commands/100706 https://postgres.ai/console/gitlab/gitlab-production-main/sessions/32629/commands/100707
How to set up and validate locally
- Ensure pipeline run on a fork show the fork badge
- Ensure pipelines that are not run on a fork do not show the fork badge
Related to #498111 (closed) and #498113 (closed)