DependencyTrack only find vulnerability issue from OSS index analyzer not from NV

### Current Behavior

I setup a dependency track server with (k8s) use helm in middle of 2022 (following the instruction from your git hub page) which installed the 4.5.0 version ( evryfs-oss/dependency-track, chart 1.4.1). I used to upload a sbom json file, which had 2000+ components and got 200+ vulnerability issues.

But recently the number of vulnerabilitites issues significiately reduced to 5. I tried other projects which get similar trend. I found all issues reported by "Sonatype OSS index" Analyzer. I cannot find any of issue from internal (NVD) any more. I had make sure internal anaylzer and the NVD mirror is on, I saw the log the DT was able to download the NVD CVE DB.

I also tried the 4.63(1.5.5, the latest chart), I got same behavior. I tried dependencytrack/bundled:lastest locally. Still same.

Do I miss anything. Because I am preparing a demo for my boss. I really need some help. Any advices are highly appriciated.

### Steps to Reproduce

1. create a project in DT
2. upload the sbom json (from the zip) in components page
3. wait for the analyze done
4. check the vuln issue number and which analyzer found it
[populated.zip](https://github.com/DependencyTrack/dependency-track/files/10670316/populated.zip)

### Expected Behavior

expect to see more vuln issues (expected 200+) found by DT, and "OSS index analyzer" should not be the only finder.

### Dependency-Track Version

4.6.x

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