Indicate when a project’s component inventory changed since the last vulnerability analysis

### Current Behavior

Manual component create, update, or delete does not start analysis, so findings and metrics can stay outdated. Clients have no durable signal that the inventory changed after LAST_VULNERABILITY_ANALYSIS.

### Proposed Behavior

Expose a project-level componentsChangedSinceAnalysis flag that is set on manual inventory edits and cleared when analysis completes.

https://owasp.slack.com/archives/C6R3R32H4/p1784642096116239

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

Start by locating the project-level paths for manual component creation, updates, and deletion, then find where vulnerability analysis completion is recorded. Trace how project-level fields are exposed to clients and identify the existing tests for inventory edits and analysis completion. Done means the flag is set by manual inventory changes, cleared after analysis completes, and remains available as a durable client signal.

Written by the indexing model from the issue text.