Improving vulnerability audit through a prioritization score

### Current Behavior

In the `Audit Vulnerabilities` tab of the project view, I identified a lack of properties useful to the prioritization of the analysis of those vulnerabilities.

The most relevant properties currently present are `CWEs` and `Severity`, which I find lacking by themselves.

### Proposed Behavior

As this enhancement request affects both frontend and backend, I will only detail the effects on the backend in the following proposition. Please review it accompanied by [its corresponding frontend issue](https://github.com/DependencyTrack/frontend/issues/1341) for completeness.

I feel the need for faster and more informed prioritization of the analysis of vulnerabilities, in particular for new projects, combining available pre-analysis metrics like CVSS and EPSS.

I propose to add a prioritization score to findings, based on CVSS base score and EPSS. I performed a simulation of various formulas ideas and arbitrated on the resulting ordering to find the formula of `priorityScore = (1 + epss^0.5) * cvss` matching my arbitration.

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