Creating policies does not scan existing projects for violations

### Current Behavior

When creating a new Policy, I would expect the system to apply the policy to all active projects. However, it seems this is not the case. Existing projects do not get any policy violations.

### Steps to Reproduce

1. Create some projects
2. Create a new policy that will trigger violations on some of the projects
3. Wait a while
4. look for policy violations - you won't find any

### Expected Behavior

I would expect the system to schedule a policy analysis on all existing projects once a new policy is created (or updated, including changes to the scope of a policy), and therefore shortly after policy creation some violations should appear, but this is currently not happening. Combined with the lack of a way to trigger this manually (#3951) one lacks a way to see the effect of a policy directly.

### Dependency-Track Version

4.13.0-SNAPSHOT

### Dependency-Track Distribution

Executable WAR

### Database Server

H2

### Database Server Version

_No response_

### Browser

Mozilla Firefox

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