Support new user groups / admin-side

[tcompa]

As of fractal-server 2.4.0, superuser will have access to these new routes

• GET /auth/group/ get list of groups, with query param user_ids=False
• POST /auth/group/ creates an empty group
• GET /auth/group/{group_id}/
• PATCH /auth/group/{group_id}/ - associates existing users to an existing group
• DELETE /auth/group/{group_id}/ (not supported, for the moment)
• GET /auth/group-names/: an auxiliary endpoint which is also available to standard users

1. New admin-area user-groups page
2. Updates to admin-area user page (e.g. show groups of user, in their own info page, and expose possibility of adding user to other groups)

[tcompa]

In fractal-server 2.4.0a0, the PATCH /auth/group/{id}/ endpoint lets us associate one group to N users (request-body attribute new_user_ids)

---

As of fractal-server 2.4.0.a1, the PATCH /auth/users/{id}/ lets us associate one user to N groups (request-body attribute new_group_ids)

WARNING: The new PATCH endpoint cannot be used to simultaneously modify the user's attributes (e.g. their slurm_user) and associate the user to new groups. This, for the moment, must go through two independent PATCH calls.

[zonia3000]

@tcompa I opened #551 as draft (no tests yet).

Can you have a look and tell me if it is everything as expected from usability perspective?

This is the admin groups page:

Does it make sense to keep also the All group in this table?

Group info page:

Group editing page implemented with drag and drop:

Possibility to add groups to the user from user editing page:

Notice that the group is added when clicking the "Add" button in the modal, not when clicking on the "Save" button of the page. Is this misleading?

[tcompa]

Great. I tried all new pages, and it works as expected.

Does it make sense to keep also the All group in this table?

I'd say yes. It's good to be sure that it exists, and we should be able to detect if a user does not belong to it (due to some error)

Notice that the group is added when clicking the "Add" button in the modal, not when clicking on the "Save" button of the page. Is this misleading?

As discussed right now, we can improve it by grouping the two API calls.

Group editing page implemented with drag and drop:

Great :)
Let's make the info/edit pages a bit more homogeneous