different result for affected projects of aliases

### Current Behavior

If a vulnerability has an alias (e.g. CVE-2023-29197 and GHSA-wxmh-65f7-jcvw), then the backend response of `/api/v1/vulnerability/source/NVD/vuln/CVE-2023-29197/projects` and `api/v1/vulnerability/source/GITHUB/vuln/GHSA-wxmh-65f7-jcvw/projects` will not return the same projects.

### Steps to Reproduce

1. have Github Advisories enabled
2. import this project [bce082ea-de4c-4d85-9ee0-67fab6027dea-inventory.cdx.json.txt](https://github.com/DependencyTrack/dependency-track/files/11610587/bce082ea-de4c-4d85-9ee0-67fab6027dea-inventory.cdx.json.txt) as it is affected by CVE-2023-29197 and wait for the analysis result
3. open https://dt-frontend/vulnerabilities/NVD/CVE-2023-29197 in a new tab and look at the affected projects. it should also have GHSA-wxmh-65f7-jcvw as an alias.
4. open https://dt-frontend/vulnerabilities/GITHUB/GHSA-wxmh-65f7-jcvw in a new tab (or reload the page due to DependencyTrack/frontend/issues/481)

### Expected Behavior

The projects affected by the alias vulnerabilities should be the same.

### Dependency-Track Version

4.8.2

### Dependency-Track Distribution

Container Image

### Database Server

PostgreSQL

### 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