Issues to apply severity and priority for Secure

Here is a list of issues without severity and priority:

• Include external vendored files ~"CI/CD", ~"Secure", ~"feature proposal"
• Garbage collect obsolete vulnerabilities stored in DB ~"Secure", ~"devops:secure", ~"feature proposal"
• Recognize a specific occurrence across multiple executions when its location has changed ~"Secure", ~"feature proposal"
• OWASP Benchmark for GitLab security features ~"Secure", ~"devops:secure"
• Styling security reports in the pipeline page ~"Secure", ~"UX ready", ~"devops:secure"
• Styling security reports in the MR Widget ~"Secure", ~"UX ready", ~"devops:secure"
• Add mean remediation time in the Security Dashboard GitLab Ultimate, ~"Secure", ~"devops:secure", ~"feature proposal", security dashboard
• SAST Job fails to detect npm project ~"Secure", ~"sast"
• Make SAST analyzers compliant with Data Model constraints Deliverable, ~"In dev", ~"Secure", backend, ~"feature proposal"
• Allow customization of Licence Management image on the fly ~"Documentation", ~"Secure", ~"feature proposal", ~"license management"
• Status of License Management in the project home ~"Secure", UX, ~"devops:secure", ~"feature proposal", ~"license management"
• List of all the dependencies in a project ~"Packaging", ~"Secure", ~"devops:package", ~"feature proposal"
• Document Security and Licence Management features permissions Deliverable, ~"Documentation", ~"Secure", ~"license management", permissions
• Security Assessment Questionnaires ~"Product Vision 2019", ~"Secure", ~"devops:secure", direction, ~"feature proposal"
• Don't change build.gradle when running the SAST find-sec-bugs-gradle tool ~"Secure", ~"devops:secure", ~"feature proposal", ~"sast"

/cc @plafoucriere