Filter project jobs by kind

What does this MR do and why?

Part 1: Introduce kind argument to API | !198134 (merged)

Part 2: Introduce kind filter to the UI (project jobs only) | YOU ARE HERE...

This MR adds the ability for users to not only find build jobs in the UI but bridge jobs (trigger jobs) as well. For now only for project jobs, we omit the admin instance for now to reduce complexity for the first iteration.

This MR solves a core issue with the product where users can see trigger jobs in pipelines but do not have the ability to see them in our main jobs view.

References

Screenshots or screen recordings

How to set up and validate locally

1. Visit Build > Jobs on a project
2. Have CI setup with trigger jobs: Docs
3. Filter for trigger jobs and build jobs with combination of filters (source, status).
4. Ensure flow works good (empty state, not results, correct results etc.)
5. Test out URL query string combinations
6. Make sure admin jobs does not have the ability to filter by kind (shared component)

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 #555434 (closed)