Include seeded vulnerability data in MRs to review for Secure

Problem

Today we don't always include vulnerabilities both current and historical when working on new secure features. This makes UX Reviews almost impossible to achieve. By not seeing vulnerability data, the review process takes a lot of FE's time on calls giving Designers instruction on how to edit and manipulate files and debug errors along the way just to see vulnerability data in their GDK.

Solution

Seed vulnerability data in the MR to review for UX so they can assess UX changes or new feature implementations as they were designed.