Draft: Add null constraint on finding_uuid to Vulnerability Feedback

What does this MR do?

Adds null constraint on finding_uuid to Vulnerability Feedback

Migration output

bundle exec rails db:migrate 
== 20210512215031 AddNullConstraintOnFindingUuidToVulnerabilityFeedback: migrating 
-- current_schema()
   -> 0.0003s
-- transaction_open?()
   -> 0.0000s
-- current_schema()
   -> 0.0003s
-- execute("ALTER TABLE vulnerability_feedback\nADD CONSTRAINT check_ca7d73127b\nCHECK ( finding_uuid IS NOT NULL )\nNOT VALID;\n")
   -> 0.0027s
== 20210512215031 AddNullConstraintOnFindingUuidToVulnerabilityFeedback: migrated (0.0286s) 

bundle exec rails db:rollback                                                                               
== 20210512215031 AddNullConstraintOnFindingUuidToVulnerabilityFeedback: reverting 
-- execute("ALTER TABLE vulnerability_feedback\nDROP CONSTRAINT IF EXISTS check_ca7d73127b\n")
   -> 0.0017s
== 20210512215031 AddNullConstraintOnFindingUuidToVulnerabilityFeedback: reverted (0.0092s) 

Does this MR meet the acceptance criteria?

Conformity

• I have included a changelog entry, or it's not needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• 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

Related to #277141 (closed)