Ignore the unnecessary columns from the `vulnerability_feedback` table

Why are we doing this work

We are in the process of deprecating the usage of the project_fingerprint attribute of the findings. By using uuid values to identify findings, we can easily associate any related entity with finding.

As we already have the uuid column in the vulnerability_feedback table, we can now remove the unnecessary columns like, project_id, category, and project_fingerprint.

Implementation plan

• backend Ignore the project_id, category, and project_fingerprint columns from the vulnerability_feedback table