Implement communities creation & members sync

[mirekys]

Related #27

For CESNET repositories, we will need to to create communities (mapped to VOs/Perun groups)
sync community members and its roles in a community with data from Perun.

For new VOs/groups requesting a repository community, the procedure would be following:

1. In Perun, create the main group for the repository community, note the UUID of the created group (this would map to the all members Invenio community role)
2. In Perun, create subgroups for each specialized community role (curator, publisher) inside the main Perun group, note the UUIDs for each role group
3. On the repository, call the following CLI command to initialize the community:

invenio oarepo:communities create --help
Usage: invenio oarepo:communities create [OPTIONS] COMMUNITY_ID TITLE

Options:
  --description TEXT  Community description
  --policy TEXT       Curation policy
  --logo-path TEXT    Path to the community logo file
  --ctype TEXT        Type of a community
  --help              Show this message and exit.

4. Wait for Perun export to push group members configuration to be synced with community members

Tasks

• Create DB table to hold Community to Perun UUID group mappings

• Create CLI command to create the community as described in the scenario above. It should also create Invenio Roles named:

  • community:$community_id:member
  • community:$community_id:curator
  • community:$community_id:publisher

• Create repository API endpoints to handle GET /community/<code>/members and PATCH /community/<code>/members

• Create a service that parses Perun users_export and creates a PATCH request using the APIs from previous step, the request body would be looking like:

[{
  "group": "<uuid>",
  "op": "add|remove",
  "user": { "id": "<uniqPersistentID>", "first_name": "<fn>", "last_name": "<ln>", "email": "<email>"}
}]