Suppressed findings are included in policy violations

### Current Behavior

If we triage vulnerabilities, set them as not applicable, and suppress them, they still appear as policy violations, and this feels counter-intuitive to me: we have triaged the vulnerability as not applicable so it's not violating the policy. I know it's possible to also manually suppress the policy violation, but ideally there shouldn't even be a violation. It would also work just fine if we could manually add a condition to the policy to have it only apply to non-suppressed findings.

### Steps to Reproduce

1.

### Expected Behavior

Suppressed findings do not lead to a violation.

### Dependency-Track Version

4.7.x

### Dependency-Track Distribution

Container Image

### Database Server

PostgreSQL

### Database Server Version

_No response_

### Browser

Google Chrome

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