Create and list memberships for generic content types

It should be generic (e.g. use ?corpus=XXX or ?repository=XXX params.
There should be a distinction between groups and users (Probably with 2 different endpoints)

• Update endpoints
• Update existing tests
• Write new test cases
• Update the frontend (see frontend#494 (closed))