Use vulnerabilities from Composer package repositories

### Current Behavior

As mentioned in https://github.com/DependencyTrack/dependency-track/issues/2337#issuecomment-2543967897, Compose package repositories also provide vulnerability information for packages.

For some vulnerabilities this is the only way to get those vulnerabilities, for example [SA-CONTRIB-2023-052](https://www.drupal.org/sa-contrib-2023-052). Neither OSS, NVD, GHSA, Snyk, OSV report this vulnerability. But for companies running lots of Drupal projects, it's important to have visibility of these vulnerabilities.

The composer package repository provides vulnerability information in two places:
- Package meta data response, i.e. https://packages.drupal.org/files/packages/8/p2/drupal/mollie.json
- API https://packagist.org/api/security-advisories/?packages%5B%5D=drupal/mollie

The API part is unclear what the URL for the Drupal 8 composer repository is. The provided example url is from the main packagist repository. This doesn not return the vulnerability.

More info about the API (and other repo functions): https://packagist.org/apidoc#list-security-advisories

### Proposed Behavior

There are multiple options Depenendcy Track can do:

- During metadata processing in `ComposerMetaAnalyzer` the vulnerability information is already returned by the package repository. These vulnerabilities could be stored in Dependency Track and used by the Internal Analyzer. Currently this is not straightforward as meta data analysis runs in parallel with or possibly after vulnerability analysis. Downside is also that it could confuse users that the repository is also a vulnerability source (could be optional flag).

- A new analyzer could be created i.e. `ComposerVulnerabilityAnalyzer` that uses the API to retrieve vulnerabilities. At the time of writing it's unclear if the Drupal specific package repository supports this API.

I am curious about other peoples thoughts.

Please note that the Composer Package Repository doesn't support PURL or CPE. But since Dependency Track already retrieves meta data by just `group` and `name`, it should be OK to do the same for vulnerabilities?

I think somewhere here on Slack or Github somebody pointed us towards a library that maps PURL/CPEs to namespace/group/name parts.

I also raised https://github.com/composer/packagist/issues/1497

### 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 enhancement was already requested