Show simple status filter for pipeline report

What does this MR do and why?

Related #433483 (closed)

When the feature flag pipeline_security_dashboard_graphql is enabled, the vulnerability list and vulnerability filter components from the vulnerability report pages are re-used in the pipeline security tab. The status filter contains options for selecting dismissal reasons. However, we can't filter findings yet by dismissal reason, so it does not make sense to allow this filtering.

Instead, a simple status filter component is added pipeline_status_filter.vue, which is heavily inspired on the status_filter.vue before it had support for dismissal reasons. The reasoning behind creating a new component (which contains much of the same code) can be found in the issue #433483 (closed).

In addition, for the pipeline status filter, we make sure that the default value is only the "Needs triage" status and not "Needs triage" and "Confirmed" which is the case on the vulnerability report page.

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

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.