choose access controll setting on manual project creation

### Current Behavior

When enabling the ACL feature, a user -- that might be assigned to several Teams -- cannot see a project they themselves created via the 'Create Project' button.
This is because the Portfolio Access Control does not auto-set the new project to any Team the user is in.

(last tested in release 4.7.0)

### Proposed Behavior

It would be nice if the user was prompted on project creation with an additional dialogue to choose which Teams (from those they belong to) should be granted access to the new project.

Does this fall in line with the intended usage of the access control?
We see this as the major blocker of enabling the ACL, since it means additional overhead for the admin to add new projects to the respective teams.

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

Start from the manual “Create Project” flow and the Portfolio Access Control behavior described in the issue. Trace how a newly created project is assigned access when ACL is enabled. Done means a user can choose among their Teams during creation and can then see the project without administrator intervention.

Written by the indexing model from the issue text.