Security vulnerabilities no longer scanned after organization change

### Current Behavior

In our test case, it appears that when an organization changes, security vulnerabilities are not caught anymore. It should be possible to either reconfigure the organization somehow, or to track these changes such that the vulnerabilities still match, also after an organization change. Example data using the django 5.0.1 framework through uv:

CVE-250-45230:

The CVE from the NVD says:

cpe:2.3:a:djangoproject:django:5.1:*:*:*:*:*:*:*
cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:* (>=4.2.0|<4.2.16)
cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:* (>=5.0|<5.0.9)

PyPI through UV and syft report:

cpe:2.3:a:django_software_foundation_project:python-django:5.0.1:*:*:*:*:*:*:*

### Proposed Behavior

It should be possible to link both organizations together and/or an online database with these links, such that the CVE still traps.

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