Improve user management

[masonlr]

Goal

Improve user management system

Acceptance criteria

• [ ] Construct simple web UI for creating/removing users.
• [ ] Support concept of nested organisations and users. i.e. an organisation can have a child organisation or a child user.
• [ ] Document procedure for creating/removing users.
• [ ] Frontend API calls are updated to accommodate any changes.

Out of scope

Implementation notes

• Current implementation is https://github.com/alan-turing-institute/science-gateway-users
• [ ] Determine whether present JWT implementation is the most appropriate/secure method. i.e. should we instead be creating a flask OAuth2 server.

[klapaukh]

We also need a clear idea of what users can / cannot do documented somewhere. I.e.

• Who can see which cases?
• Who can see which results of cases?
• Who can see what jobs were run?
• Who can create new users?
• Who can create template values for jobs?
• Who can see template values for jobs?
• Who can create cases?
• Is money global to everyone or per user?
• Who can add funds?
• Who own what kind of 'stuff'? Users? Organisations? Do users just act as one person organisations?
• If you are an admin for organisation A, then are you also an admin for all of it's children?

[masonlr]