Feature Request/Idea: Create new Institutional Admin role in-between SuperAdmin and Admin for Institutional Collections Managers

Overview of the Feature Request
This new role will be created for institutional collections administrators who oversee institutional collections in multi-institutional Dataverse installations. Increasingly the default 'Admin' role in DV is not quite sufficient for use for these collections administrators since they oversee a diverse collection which may include researcher's Dataverse Collections that have the Admin privileges assigned at the same level. Some issues that have arisen with Admin role is that there isn't any differentiation between the Institutional Admins and the regular researcher / depositor / collection Admins , which can cause conflict when individuals from the institutional admin group are removed from the Admin permissions of a Collection / and/or the institutional admins are not able to monitor those collections.

What kind of user is the feature intended for?
Since this is new Admin role, this would be intended for institutionally appointed staff who oversee Dataverse services for their institutional collections.

What inspired the request?
Many institutional admins request this feature in the Borealis multi-institutional installation setup because they require a level of permission to be able to oversee all collections and datasets for their institutional collection space in Borealis. Currently SuperAdmin is not given to anyone outside of the Borealis technical team.

What existing behavior do you want changed?
Permissions and roles for Admin, to create new role in between SuperAdmin and Admin calling it 'InstitutionalAdmin'. This permission level does not currently exist in Dataverse for us to create it as a custom role.

Any brand new behavior do you want to add to Dataverse?
Yes this new permission and role be added to the permissions options in DV and ability to assign to individual or group members who are institutional admins.

Any open or closed issues related to this feature request?

The issue does not name files, tests, or entry points. Start by mapping the existing Admin and SuperAdmin permission definitions and assignment paths, then clarify which institutional scope and permissions InstitutionalAdmin should have. Done means the new role can be assigned to users or groups and its permission boundaries are covered by tests.