Improve consistency on the web-api across all shareable resources

[pcrespov]

The web-api exposes some shareable resources, namely project, tag, wallet, workspace, service. We need ensure consistency on the sharing interface across all of them:

1. share operations: should be shared using the same approach
   • GET /tags/{tag_id}/groups returns list fo
   • POST /tags/{tag_id}/groups/{group_id} with access_rights: to share tag_id with group_id with given access_rights
   • PATCH /tags/{tag_id}/groups/{group_id} with access_rights: to update access
   • DELETE /tags/{tag_id}/groups/{group_id} to unshare
2. CRUD operations: resource schema must include myAccessRights
   • GET /tags/{tag_id} -> TagGet and TagGet.myAccessRights
3. access layers:
   • role-based access
   • group-based access
   • constraints on special groups e.g. tag cannot be shared with everyone group or wallet can only be shared among users (i.e. primary groups)
   • invalid access rights e.g. read=False, write=True, delete=True
   • ...
4. errors when operating resource
   • resource not found (404)
   • operation on resource forbidden (403) (i.e. caller has no access rights to perform an operation on this resource)
   • ...

[odeimaiz]

support /workspaces:search?filters={trashed:true}

[odeimaiz]

modified_at
modified_by