Portfolio access control based on project tags

### Current Behavior

In Dependency-Track, access to projects in the portfolio can be restricted through teams using the Portfolio Access Control configuration. Currently, access must be granted on a per-project basis.

This means that administrators need to explicitly assign each project to the corresponding teams. When a new project is created, it is not automatically accessible to any team, even if it logically belongs to a group of projects already accessible to that team. As a result, administrators must manually update the Portfolio Access Control configuration every time a new project is created to grant the appropriate permissions.

This process creates additional administrative overhead and may temporarily prevent teams from accessing projects they should normally have access to.

### Proposed Behavior

Allow portfolio access permissions to be granted to teams based on project tags, in addition to the existing per-project permissions.

With this approach, administrators could configure a team to automatically have access to any project that contains a specific tag. For example, a team could be granted access to all projects tagged with a particular value (e.g., environment, department, or application domain).

If a new project is created with a tag that is already associated with a team’s permissions, the team would automatically gain access to that project without requiring manual intervention from an administrator.

This would reduce administrative overhead, simplify access management, and ensure that teams automatically receive access to newly created projects that match their scope.

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