Trigger analysis immediately when an internal vulnerability is created or updated

### Current Behavior

Findings for INTERNAL vulnerabilities are only produced when components are analyzed , on BOM upload or during the scheduled portfolio analysis. Creating or updating an internal vulnerability has no immediate effect: findings appear silently up to 24 hours later, and there is no feedback if the affected-component identifiers (PURL/CPE) match nothing in the portfolio (e.g. due to a typo).

### Proposed Behavior

When an INTERNAL vulnerability is created or updated, resolve candidate components with targeted queries and dispatch an InternalAnalysisEvent for just those candidates. The existing internal analyzer performs the precise identity and version-range matching, so results are identical to those of the scheduled analysis — they just appear immediately. A companion frontend change adds a Tracked/Untracked badge so users can see at a glance whether an internal vulnerability matches anything in the portfolio.

### Checklist

- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/main/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

Trace the create and update flow for INTERNAL vulnerabilities and compare it with the existing scheduled portfolio analysis and internal analyzer. Identify how candidate components and InternalAnalysisEvent are currently reached, then inspect the frontend vulnerability view for the proposed Tracked/Untracked badge. Done means matching findings appear immediately for affected components and the UI shows whether an internal vulnerability is tracked.

Written by the indexing model from the issue text.