DependencyTrack treats newer version as vulnerable while it is not

### Current Behavior

Our DependencyTrack instance is currently reporting Microsoft.Data.SqlClient version 5.2.0 as vulnerable for CVE-2024-0056. According to [the CVE](https://www.cve.org/CVERecord?id=CVE-2024-0056) that vulnerability only exists in versions 2.1.7, 3.1.5, 4.0.5 and 5.1.3, but not 5.2. I've asked the maintainers of this package what the regular procedure is and whether the CVE needs updating, but according to them that is not how it is supposed to work which makes sense since that would create a maintenance hell. See https://github.com/dotnet/SqlClient/issues/2391 for reference.

### Steps to Reproduce

1. Upload the attached BOM to DependencyTrack [bom.json](https://github.com/DependencyTrack/dependency-track/files/14775575/bom.json)
2. DependencyTrack shows the project as being vulnerable for CVE-2024-0056

### Expected Behavior

I would expect DependencyTrack to not show version 5.2.0 of Microsoft.Data.SqlClient as being vulnerable

### Dependency-Track Version

4.10.1

### Dependency-Track Distribution

Container Image

### Database Server

PostgreSQL

### Database Server Version

_No response_

### Browser

Google Chrome

### 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 defect was already reported