Refactor specs to not use `vulnerabilities_finding_pipeline` directly
What does this MR do and why?
We are working on an epic to drop the
vulnerability_occurrence_pipelines table.
When we eventually migrate off of this table/model, there are many
specs that will need to be updated to no longer use the
:vulnerabilities_finding_pipeline factory
This refactor to the Vulnerability::Finding factory centralizes the
pipeline association to the FactoryBot layer, rather than having the
association happen at the spec level.
This change will prevent the future MR (migrating off of this table/model) from including a lot of tangentially related spec changes
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.
How to set up and validate locally
- CI still passes
related to: #422384 (closed)
resolves: #450524 (closed)