Convert Issues::CreateFromVulnerabilityService to work similar to Issues::BuildService

Summary

The following discussion from !40958 (merged) should be addressed:

• @reprazent started a discussion: (+2 comments)

  Did we consider building an issue and presenting the issue form with this information pre-filled. That way, the user has the opportunity to adjust the issue if they wanted to.

  We do something similar for resolving discussions in merge requests using a new issue in the Issues::BuildService.

  Do you think that would be more consistent?

Implementation plan

• backend Create new Issues::BuildFromVulnerabilityService to base off of Issues::BuildService (!47510 (merged))
• backend Edit new route in IssuesController that uses the new service if a vulnerability parameter is included (#283950 (closed))
  • Make sure we create a Vulnerabilities::IssueLink after the issue is persisted in the subsequent create call.
• frontend Update front-end to call new route (#284376 (closed))
• backend Remove existing code that is no longer being used (Issues::CreateFromVulnerabilityService) (#284396 (closed))

NOTE: MR !46503 (closed) was originally created for this issue, but became too complex and is being broken down into multiple MRs.