HW BOM analysis

### Current Behavior

Dependency-Track is currently focused on monitoring software vulnerabilities through SBOM analysis and works well for software components whose CPEs or package identifiers can be resolved automatically.

However, when dealing with hardware BOMs, vulnerability monitoring becomes much more difficult because hardware components usually do not have automatically associated CPEs. As a result, hardware-related vulnerabilities cannot be continuously tracked in the same way as software vulnerabilities.

This creates a gap for products that must comply with regulations such as RED 18031 and the Cyber Resilience Act (CRA), where both software and hardware cybersecurity aspects must be monitored over time.

### Proposed Behavior

I would like Dependency-Track to support hardware BOM vulnerability monitoring in addition to software vulnerability monitoring.

In particular, it would be useful if hardware components from an HBOM could be associated with potential CPEs through automated or semi-automated matching mechanisms. Since hardware CPE mapping is often ambiguous and cannot always be resolved automatically, the system could provide candidate CPEs with confidence levels or allow manual validation.

Ideally, Dependency-Track should also continuously search for newly available or updated CPEs related to hardware components, so that vulnerability monitoring remains active over time for the hardware BOM as well, similarly to how SBOM monitoring currently works for software components.

[e88_hbom.json](https://github.com/user-attachments/files/27445423/e88_hbom.json)

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