Add a ManagePrivateURL permission

Overview of the Feature Request
Splitting off a new ManagePrivateURL permission from the current ManageDatasetPermissions permission to manage Private URL and URLs for Anonymized Access

What kind of user is the feature intended for?
Dataverse collection or dataset administrators

What inspired the request?
Currently the ManageDatasetPermissions permission allows, in addition to managing dataset permissions, to manage Private URLs.
This has proven both confusing and limiting for installations:

• https://github.com/IQSS/dataverse/issues/9938
• https://github.com/IQSS/dataverse/issues/9190

Splitting a ManagePrivateURL from ManageDatasetPermissions would make the list of permissions clearer and allow installations to better adjust roles' permissions to their needs.

What existing behavior do you want changed?
Remove the ability to manage Private URLs and URLs for Anonymized Access in the ManageDatasetPermissions permission

Any brand new behavior do you want to add to Dataverse?
Add a new ManagePrivateURL permission with the following rights:

• creating a private URL
• disabling a private URL
• creating an URL for Anonymized Access
• disabling an URL for Anonymized Access

with the following description: "Manage Private URL or URL for Anonymized Access for a dataset"

Any open or closed issues related to this feature request?
Aforementioned issues on Permissions granularity:

• https://github.com/IQSS/dataverse/issues/9190

and specifically Private URL (but broader):

• https://github.com/IQSS/dataverse/issues/9938

Will you be able to contribute a Pull Request for this issue?
Yes, although it is not currently in our priorities for the coming month so feel free to start working on it if this is more urgent to your installation!

Thoughts for the future
For us, a distinction between Anonymized Private URLs (URL for Anonymized Access) and "regular" Private URLs is not currently a need, but it would be interesting to have other installations opinion on whether URL for Anonymized Access should, in the longer run, have a dedicated permission, separate from ManagePrivateURL or not.

Start by tracing the existing ManageDatasetPermissions checks and permission definitions for Private URLs and URLs for Anonymized Access. Identify the paths for creating and disabling both URL types, then verify that the new ManagePrivateURL permission controls those four operations while ManageDatasetPermissions no longer grants them.