portfolio access management mechanism for alerts

### Current Behavior

How do you do?

We are on version 4.12.4 and are very pleased that the portfolio access management (beta) is now also a very useful feature of the dependency track. As we have different teams with sometimes many projects and versions, this is exactly what we need to be able to use the application well at enterprise scale.

What we are still missing is the ability to configure the notifications/alerts in the same way as the portfolio access management.

So far, the notifications can be restricted based on projects or tags, but this does not reflect the authorizations of the different teams.

### Proposed Behavior

Ideally, it would also be possible to implement the delivery of notifications in the same way as the portfolio access management authorizations. So we would now also like to be able to link a team for each configured alert.
Alerts should only be executed if the projects for which the alert was triggered can be viewed by the team (or teams) that were also referenced in the alert.

project -> belongs to team
alert -> belongs to team
==> Alerts are only triggered for projects that are assigned to the same team as the project.

It would be a real pleasure if it would be possible to complete the portfolio-access-managament also by mapping it in the alert configuration!!!

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