Dependency-track parser should include Vulnerability Alias information

[lme-nca]

Bug description
Dependency-track includes Vulnerability alias information in the FPF format export. This information is currently ignored by the Parser, however if correctly read and set in VulnerabilityId it could help do better deduplication.

Steps to reproduce
Steps to reproduce the behavior:

1. import FPF format findings from Dependencytrack or Set up Dependencytrack Defectdojo integration
2. see that the VulnerabilityID field only contains 1 entry
3. see that the FPF format can contain multiple ids (depending on analyzers active in Dependency-track)

Expected behavior
The "vulnerability_id" in the dependency-track parser reads all the aliases as well

Deployment method (select with an X)

• Docker Compose
• [ x] Kubernetes
• GoDojo

Environment information
custom hosting k8

Logs

Sample scan files
If applicable, add sample scan files to help reproduce your problem.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context (optional)
This issue relates to some other issues in dependency-track:
1 bug: DependencyTrack/dependency-track#2469
but also the discussions about deduplication on Dependencytrack side here:
DependencyTrack/dependency-track#1994
and here: DependencyTrack/dependency-track#1912 (comment)

[lme-nca]

fixed in #7746 and #7583