feat(oh2-287): admin user group crud

[gasp]

See oh2-287.

• better handling of user&group tabs (allowing direct access via location state)
• create a new usergroup
• edit usergroups
• manage usergroups permissions
• delete a usergroup

create a new usergroup

edit a usergroup

manage usergroup permissions

delete a usergroup

[gasp]

@mwithi This is using the soon-to-be-deprecated permission api.
Should I disable usergroups' permissions management from this PR?

[gasp]

depends on
informatici/openhospital-api#464 and informatici/openhospital-core#1391

[mwithi]

@mwithi This is using the soon-to-be-deprecated permission api. Should I disable usergroups' permissions management from this PR?

I think you can wait for the API and then adjust this PR, is it ok for you? Thanks!

[mwithi]

depends on informatici/openhospital-api#464 and informatici/openhospital-core#1391

both merged!

[mwithi]

This must remain unchanged @SilverD3 ?

[SilverD3]

Yes. See this comment,

[mwithi]

Integration tests seem good, but I would add a "select all" for columns and rows in the permission page.

Sorry if I don't remember: the user creation with its password encrypted is part of another issue/PR?

[gasp]

Integration tests seem good, but I would add a "select all" for columns and rows in the permission page.

Can we add this as a future iteration? this pull request is already humongous!

[gasp]

Sorry if I don't remember: the user creation with its password encrypted is part of another issue/PR?

Password is related to user, this is usergroup. AFAIK, password encryption is handled backend and does not (should not) affect frontend.

[SilverD3]

@gasp I shared a video on slack, showing the result on my machine.

1. You can see that the sidebar width grows based on the content of page. You could fix it by controlling the width of the "content display area", I mean the area where we show the content of the selected menu. I remember I've reported that issue in the pass and the fix I applied just worked for the component I was working on.
2. The changes diff you show doesn't work properly. While editing a user group, if check and uncheck the same permission, you'll log it in the changes list (as a permission to revoke)
   
3. The reset button doesn't work
4. Maybe you should wait (show a loader) until all the data has been loaded before displaying the edition form. You can see in the video that when I navigate to the user group edit page, some labels show and it's after about 2 or 3 seconds that form fields show.
5. In the user group edit page, I suggest to use a scrollable component (div) or a collapsible one to display the permission list, so we don't have to scroll too much to reach form actions
6. Until the endpoint for updating a group by passing the list of permissions is improved, you could use what I showed you at the meeting rather than making as many API calls as there are permissions.

PUT /users/groups/

// Request body
{
  "code": "labo",
  "desc": "Staff members working in the laboratory",
  "permissions": [
    {
      "name": "string",
      "id": 0,
      "description": "string"
    }
  ]
}