Add dynamic filters for scanner/vendor

What does this MR do?

Add ability for dynamic filters for reportType/scanner

Users can configure independent 3rd-party scanners and this MR dynamically generates those filters. It always creates the GitLab filters we all know and love, but then creates independent filters (i.e. Dast - custom scanner this means that now when a user selects a reportType filter (what we call Scanner in the UI), it is not just the reportType being searched for (i.e. DAST, SAST, etcetera), but also the scanner itself (i.e. Gemnasium, custom-scanner-dast, etcetera), so the reportType filter is now two filters in one.

To achieve this, I must first retrieve the project-specific filters, and create the filter options, and then make it so when the user selects one of the filters, it searches by both reportType and scanner

Screenshots

DEMO
https://www.youtube.com/watch?v=HNOwyGJy-Wc&feature=youtu.be

NOTE: The checkmarks are not correct in the second image; only one should be selected.

-	Before	After
-
-

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #229661 (closed)