Same vulnerability different databases reported twice

### Current Behavior

A vulnerability which exists in multiple databases are not linked so report as 2 issues (therefore doubling risk score)

### Steps to Reproduce

1.import BOM with vulnerability present that reported in NVD, GitHub and Sonatype

### Expected Behavior

Vulnerability are linked and only report once

### Dependency-Track Version

4.6.2

### Dependency-Track Distribution

Container Image

### Database Server

MySQL

### Database Server Version

_No response_

### Browser

Google Chrome

### Checklist

- [X] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [X] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported