Add `NOT NULL` constraint for `security_findings` on `uuid` column

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.

Implementation plan

• backend Create a migration to add NOT NULL constraint on uuid column of the security_findings table