Update database schema to make use of vulnerability DB

### Current Behavior

We're aiming to build a mechanism to assemble and distribute a vulnerability database tailored to Dependency-Track's needs.

The goals for our own database are defined here: https://docs.google.com/document/d/1DVV4ik7NGOBc6u-fdPlPVKoplNmSpzDT6iC4FJAFYi0/edit?tab=t.0#heading=h.w22q0gsagz1c

Dependency-Track's own database schema will need to be updated to make effective use of the data provided by this effort.

### Proposed Behavior

Update / refactor the schema to make effective use of the data provided by this effort. Keep in mind that existing data will need to be migrated.

> [!NOTE]
> Partly depends on #4528, in order to know what fields will be provided.

Relevant classes (i.e. tables) of the current schema are:

* [Vulnerability](https://github.com/DependencyTrack/dependency-track/blob/master/src/main/java/org/dependencytrack/model/Vulnerability.java)
* [VulnerabilityAlias](https://github.com/DependencyTrack/dependency-track/blob/master/src/main/java/org/dependencytrack/model/VulnerabilityAlias.java)
* [VulnerableSoftware](https://github.com/DependencyTrack/dependency-track/blob/master/src/main/java/org/dependencytrack/model/VulnerableSoftware.java)

TODO: Add Mermaid ER diagram.

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