Introduce security scan model

What does this MR do?

Introduces a Scan record to the Database whenever a Secure Product is successfully run as part of a build. Secure Products produce JobArtifacts with a file_type one of sast|dast|dependency_scanning|container_scanning.

The introduction of the Scan record will enable the Secure Team to determine the difference between a build running that didn't run any Secure Products, and a build that ran a Secure Product that produced zero vulnerabilities.

This MR in part relates to #10250 (closed).

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• [-] 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

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