Ignore the unnecessary column position from the security_findings 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 attribute for security_findings, we can remove the unnecessary columns from this table.

Implementation plan

• backend Ignore the position column from the security_findings table