Vulnerability Details Tab " Affected Components" empties

### Current Behavior

After updating an internal vulnerability via API the tab "Affected Components" becomes empty even though it is visible after quering the vulnerability that it still has them and an analyzer can still match the vulnerability to said components correctly.

### Steps to Reproduce

1.Create an internal vulnerability - preferably with an affected component.
2.Update the vulnerability using the API by either adding another affected component or changing the existing affected component.

### Expected Behavior

I would expected the tab to display all current affected components that a vulnerability has.

Currently my workaround is to delete and then recreate the vulnerability with it`s updates.
Seeing how there is no add or option to the tab on the frontend and tracking how external vulnerability dbs are rebuild regularly, perhaps that is the actually intented way to do it?

### Dependency-Track Frontend Version

4.10.0

### Browser

Other

### Browser Version

Chromium Version 123.0.6312.122

### Operating System

Linux

### 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/frontend/issues) for whether this defect was already reported

Start by reproducing the issue in the Vulnerability Details tab: create an internal vulnerability with an affected component, update it through the API, and inspect the Affected Components tab. Done means the tab displays all current affected components after adding or changing one through the API.

Written by the indexing model from the issue text.