Feature Request: make role assignment for newly created collections flexible/configurable

Overview of the Feature Request

Many installations may not want their users to publish data without review, but would like them to organize data into collections per project, etc.

As anyone who has the "AddDataverse" permission bit in a parent collection set will receive "Admin" privileges on sub-collections (hardcoded in CreateDataverseCommand), this should be adaptable to different use cases.

There are multiple ways to address this (global setting, per parent collection, inheritance, escalation/limitation, ...), so this issue is not yet a full proposal how to go about this.

For datasets within the collection a similar thing already exists - an admin can choose to assign restricted roles on newly created datasets:

What kind of user is the feature intended for?
Curator, Depositor

What inspired the request?
The current workaround is to not allow users to create collections, but ask stewards/curators instead to do it for them. This can be quite cumbersome.

What existing behavior do you want changed?
No longer hardcoded admin privilege assignment on new collections.

Any brand new behavior do you want to add to Dataverse?
Nope.

Any open or closed issues related to this feature request?

• #11802

Are you thinking about creating a pull request for this feature?
Maybe.