Global Audit Vulnerability of CVE/component relationships (false positives)

### Current Behavior

Currently, Dependency-Track allows marking vulnerabilities as FALSE_POSITIVE only at the project level and for a specific component version.

This means that when a CVE is incorrectly associated with a component (e.g. CVE-1999-1278 incorrect or overly broad CPE matching), users must manually suppress the finding for each project and each affected version.

In environments where the same component is used across multiple projects, this leads to:
- Repetitive manual triage
- Increased operational overhead
- Inconsistent suppression (some projects may still report the false positive)

There is no built-in mechanism to define a global suppression rule for a CVE/component relationship.

### Proposed Behavior

Dependency-Track should provide a way to define global suppression rules for vulnerabilities.

Specifically, it should be possible to mark the relationship between a CVE and a component (or component identifier, e.g. purl / CPE) as a FALSE_POSITIVE at a global level (across all projects).

This would allow users to suppress known false positives once, instead of repeating the same action across multiple projects.

Why this is needed:
- Improves scalability in real-world usage where components are reused across many projects
- Reduces repetitive manual work
- Minimizes noise caused by incorrect vulnerability mappings (e.g. [NVD inaccuracies](https://github.com/DependencyTrack/dependency-track/issues/5991))
- Increases trust in vulnerability analysis results

This feature would be especially useful for handling known ecosystem-wide false positives (such as incorrect CVE-to-component mappings).

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