Write delegation for resource administrator

[chibenwa]

Upon adding resource administrator (update and creation)
Also position a write delegation onto the resource calendar for each administrator

Upon removing resource administrator (update and delete)
Also revoke this administrative right

Implements a route POST resources?task=repositionWriteRights that for each resource reset the write rights to the actual population of administrators (used eg for migration).

Definition of done: Resource administrator can update resource participation from OpenPaaS calendar SPA

Technically:

curl 'https://dav.linagora.com/calendars/{domainId}/{resourceId}.json' \
  -H 'Authorization: Bearer TECHNICAL_TOKEN' \
  -H 'Accept: application/json, text/plain, */*' \
  -H 'Content-Type: application/json;charset=UTF-8' \
  --data-raw '{"share":{"set":[{"dav:href":"mailto:admin@linagora.com","dav:read-write":true}],"remove":[]}}'

curl 'https://dav.linagora.com/calendars/5f50a663bdaffe002629099c/5f50a663bdaffe002629099c.json' \
  -H 'Authorization: Bearer TECHNICAL_TOKEN' \
  -H 'Accept: application/json, text/plain, */*' \
  -H 'Content-Type: application/json;charset=UTF-8' \
  --data-raw '{"share":{"set":[],"remove":[{"dav:href":"mailto:twake-calendar-dev@linagora.com"}]}}'

[chibenwa]

As part of grooming test that giving read-write right on resource calendar for the admin user is enough for hin to accept attendance in the name of a resource in OpenPaaS Calendar SPA.