Creating Issues associated with Vulnerabilities - backstage
## Overview
According to [the engineering discovery](#10252) on the First-class Vulnerabilities, the [MVC version of First-class Vulnerabilities](#13561) (aka "MVC Standalone Vulnerability objects") will provide the ability to
> Allow `Issue` and `Vulnerability` objects to be linked to each other with a many-to-many relationship
This issue is for tracking the following:
- the data model changes to support such linking between Issues and Vulnerabilities
- new operation(s) for the [new Vulnerabilities API](#10242)
It was extracted into a separate issue scheduled for %"12.5" because [it turned out](https://gitlab.com/gitlab-org/gitlab/issues/10242#note_220073830) that these changes were stretching the scope of #10242 too much for %"12.4".
## Development log
### Status
- [x] Data model changes to support many-to-many linking between Issues to Vulnerabilities
- [x] New operation(s) for the Vulnerabilities API
- [ ] ~~Update the Vulnerabilities API documentation stubs to document new API calls~~
### Decisions
issue