Set up ERM permissions model

I think we should avoid creating a new module, as that seems like unnecessary resourcing just to bootstrap some data. Instead I propose we just implement the necessary system level interface(s) probably something like 'tenantPermissions' and do the right thing within each app. Think this should probably be added to the shared okapi module so that we can just add config to our app(s) and they will do the right thing on startup.

We perhaps need a data bootstrapping task in general with this as a sub-task.

So in chatting with Wayne, it sounds like the most correct way to do this would be to create a module that we'd add to Okapi that would, as part of it's tenant initialization, create permission sets (to group the permissions), and then to create the required users, permission users, credentials, service points users, etc, and assign the appropriate permission sets to them.

This is preferable to simply provisioning the information via Ansible, because the current trend is to move away from that and have all of the data provisioning handled by the modules themselves.

An example in an RMB module (though we wouldn't have to use RMB) is here: https://github.com/folio-org/mod-inventory-storage/blob/0a24f1bf854c4e2624bb14d9f912c23034e3eb35/src/main/java/org/folio/rest/impl/TenantRefAPI.java#L77

From discussions on Sprint 61 planning call, this appears to be a matter of having the permission sets created on the test system by default, and by assigning these permissions to specific users in the system.

Plan to reach out to Wayne to discuss this configuration.

I've updated the description a link to the spreadsheet of permissions based on ERM stories.

There are probably more to define from pre-ERM (jira project) days. Please correct the description if the default user privilege is not that all data on ERM can be viewed by a logged-in user.