Use standard filter for scanner filter on non-project level vuln report

What does this MR do?

On the vulnerability report, there is a scanner filter dropdown:

Previously, we switched to a new scanner filter that groups the scan types (SAST, DAST, etc) by vendor if there are custom vendors:

However, a bug was found that shows incorrect results (no results are shown when there really are) on the group-level and instance-level reports if more than one project use a scanner with the same ID: #332727 (closed)

Because it will take some time to investigate and fix the bug, and it's already affecting live customers, we will temporarily revert back to the older, "standard" scanner filter that doesn't group by vendor for the group-level and instance-level reports.

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Related to #332727 (closed)