Improve bot comments regarding newly detected CVEs that are not introduced in the merge request

Summary

Newly detected CVEs in projects where the new dependency graph based analyzer runs results in policy violations lacking context, such as a path to where the dependency is managed and the CVE identifier.

Steps to reproduce

1. Create a project running the DS analyzer with dependency graph.
2. Create a policy blocking critical/high/med sev findings.
3. Generate DS results.
4. Observe the policy bot comments.

Example Project

What is the current bug behavior?

1. While the DS findings are present, it's not clear that these findings are identified outside of the MR (potentially in the target branch or even external to the project).
2. There's not a clear path/link to direct developers to the location where this is managed.
3. There isn't a CVE provided.

What is the expected correct behavior?

1. More details in the bot comment regarding location of the dependency and the CVE.
2. More clarity in that the dependency is detected outside of the source branch and how to action it.

Relevant logs and/or screenshots

See customer notes doc (internal).

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.