Include the User's role as part of the FF User object

[joepavitt]

Requested by https://app-eu1.hubspot.com/help-desk/26586079/view/233410279/ticket/81753305284/thread/10024322274#email

Authorisation within the Dashboard logic can be easier managed and maintained by exposing the FF roles, such that logic can be defined to permit access accordingly.

Implemented via:

• Include user role in profile object when authenticating FlowFuse/nr-launcher#322
• Add user role in auth object FlowFuse/device-agent#363

[joepavitt]

Adding to 2.15, as this may be a 10 minute task, if it is, we can ship imminently.

[knolleary]

It's a 60 minute task rather than 10 minute task.

Currently our auth plugin gets the user profile information via an authenticated call to /api/v1/user. This is not in context of a team, so cannot include team role information. We'll need to add a second call to /api/v1/teams/:teamId/user which returns:

{"role":50}

which we can then map back to the role description.

[knolleary]

[knolleary]

PR's raised against both launcher and device-agent.

[knolleary]

I'm going to close this as the required updates have been merged to launcher (for hosted) and device agent (for remote).

Launcher update will be available on FFC as part of the stack update in this week's release.

New Device Agent will be published this week.