Move pipelines page to GraphQL - Part 4

What does this MR do and why?

Part one: !206072 (merged) ✅

Part two: !207467 (merged) ✅

Part three: !208865 (merged) ✅

Part four: YOU ARE HERE 😄

Goal: Move Build > Pipelines to use GraphQL as the SSOT for data. In part four we add empty state and tabs/nav control. Query params and All count will be in the next MR.

References

Screenshots or screen recordings

How to set up and validate locally

1. First visit Build > Pipelines and ensure existing feature works as expected.
2. Next enable Feature.enable(:pipelines_page_graphql) && Feature.enable(:fix_graphql_offset_pagination_preloads) feature flags
3. Visit Build > Pipelines again
4. Ensure tabs, nav controls etc. works as expected.
5. It's okay that the rest is missing and broken, we are iterating here (I.E count, query params etc)...

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 #223264