Add VulnerabiltyFindingEvidence model

What does this MR do?

This MR creates a new model for Vulnerability Finding Evidence. This model will be replacing metadata in the finding. We are not using this table yet, that will be handled by a future MR. Related to #239179

Screenshots (strongly suggested)

Database

rails db:migrate
== 20210326190903 CreateVulnerabilityFindingEvidences: migrating ==============
-- create_table(:vulnerability_finding_evidences, {})
-- quote_column_name(:summary)
   -> 0.0000s
   -> 0.0152s
-- quote_table_name("check_5773b236fb")
   -> 0.0000s
-- quote_table_name(:vulnerability_finding_evidences)
   -> 0.0000s
-- execute("ALTER TABLE \"vulnerability_finding_evidences\"\nADD CONSTRAINT \"check_5773b236fb\" CHECK (char_length(\"summary\") <= 8000000)\n")
   -> 0.0010s
== 20210326190903 CreateVulnerabilityFindingEvidences: migrated (0.0237s) =====

rails db:rollback
== 20210326190903 CreateVulnerabilityFindingEvidences: reverting ==============
-- drop_table(:vulnerability_finding_evidences)
   -> 0.0031s
== 20210326190903 CreateVulnerabilityFindingEvidences: reverted (0.0122s) =====

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • [-] I have not included a changelog entry because _____.
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability 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
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

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