Update old fingerprints on non-default branch vulnerability feedback

What does this MR do?

• Adds a migration that updates old fingerprints on vulnerability feedback to the new fingerprint version. This will re-associate these feedback with the occurrences they were created for.
• Deletes feedback if the customer created a new feedback of the same type for the vulnerability
• Only updates feedback from dependency scanning and container scanning reports, since only those reports have a mismatch in how fingerprints used to be calculated

Issue: https://gitlab.com/gitlab-org/gitlab-ee/issues/10561

Feedback on the default branch will be fixed with: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/32292

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry for user-facing changes, or community contribution. Check the link for other scenarios.
• Documentation created/updated or follow-up review issue created
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Performance 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

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