Make vulnerability report more reusable

Previously, vulnerability_report.vue was hard-coded to only support the development and operational tabs on the standard vulnerability report:

However, we now also have agent_vulnerability_report.vue and pipeline_vulnerability_report.vue. These 2 reports need more configuration than what vulnerability_report.vue supports, so currently, rather than use vulnerability_report.vue, they instead copy what it does. This is not ideal because if we need to change vulnerability_report.vue, it needs to be done across 3 places instead of just 1.

This MR refactors vulnerability_report.vue to make it more reusable by letting the parent component control more of its behavior. For example, the fields and filters properties are no longer hard-coded and have been made into props. This will allow us to switch the agent and pipeline reports to use vulnerability_report.vue rather than copy what it does in a follow-up MR (!85305 (merged)).

Related to #357599