Create a campus admin role in ojs

[alainna]

What

Create in subi a new role: campus administrator.

A campus administrator has all the permissions of a unit or series administrator, with one exception: they do not receive submission/update notifications for content in a series, unless they are also an "admin" of that series.

A campus administrator also has permission to do certain actions which are limited to SuperUsers:

• modify unit configuration: unit name
• modify unit users
• modify certain text pages
• create/modify series and sub-units under their campus
• cannot create new campus-level units
• cannot edit or hide restricted pages (policyStatement, submissionGuidelines)

When a new unit or series is created under a campus oru by a SuperUser, the campus admin should immediately receive campus admin permissions to that unit/series.

---

@myucekul notes in #894_

eschol_roles table in OJS DB contains role and unit_id mapping for users. Currently there are three types of roles in eschol_roles:
admin
stats
submit

eschol_superuser info is saved in user_settings.

We'll likely create a new role "campusadmin" and save that in DB settings. Should we apply campusadmin role to all units or just use code to deduce campus unit admin role and provide admin level functionality. That should be simpler since we don't need to get all units in a campus tree and apply "campusadmin" to all.

[myucekul]

I don't think we need any change in OJS. subu functionality will create the campus admin user in OJS tables.