Group users for connect access

[asegun-cod]

[asegun-cod]

The current logic we have implemented is

• We created groups: one for each trust, a group for demo users and a developer group.
• The developer group members can control the trust they want to see by setting the DEFAULT_TRUST environment variable from Connect setting.
  see 3e3d5b2 and 25976a5

at the moment if any member of the developer group changes the DEFAULT_TRUST variable, this will restart the app session, therefore if any user in another group is currently working, their session will be killed and they will have to refresh.

We need to investigate this well to be sure it's a real issue and if it is then we need to be able to work around it.

[tomjemmett]

there are some considerations for this:

1. user access to the application should be via the groups, and users shouldn't be granted direct access to the application
2. as mentioned above, the DEFAULT_TRUST envvar controls the data that is shown for the developers group. however, this controls what is seen for everyone in that group. one option may be to control the data shown via a url query parameter (e.g. ?trust=X)
3. the value for the golem active config is required to happen early in the server function as data is statically loaded. If the data could be converted to a reactive then we could add a trust dropdown where the values are populated from the groups that a user is a member of (or, everything for the developers group)