Filter jobs by "kind"

Problem

Currently Build > Jobs only returns the Ci::Build type. This leads to issues where users are confused on where their jobs are at. They can see trigger jobs on the pipeline view but not on the jobs view. Which can lead to issues like #379141 (closed) surfacing. We need parity across all our CI views.

Proposed Solution

I attempted to solve this issue with the MR !195869 (closed) where we return all job types by default using Ci::Processable with the job finder. However we started to run into some issues especially around preloads and potential performance impacts.

A much better solution would be to introduce a new kind filter to the UI.

This filter will at first have Trigger as an option (more in the future for external jobs potentially) that then can use the project_jobs_resolver.rb in conjunction with the jobs_finder.rb to filter jobs by type of Ci::Bridge. We can utilize filtered_preloads https://docs.gitlab.com/development/api_graphql_styleguide/#optimizing-resolvers to dynamically preload fields like job_artifacts based on query arguments.