Added user "realm roles" to `user list`

[joshburt]

What?

• Added realm roles a user is assigned to when using the user list command.

Example Usage

List as a table

List as json

Why?

• We've had a client request for additional user level control. Specifically the ability to expose and operate on a user's roles.

How?

• I was able to find the related KeyCloak API documentation. We can request all realm roles, then all users mapped to those roles. With this detail we can merge the role assignments with the user data we already have.

How was this tested?

• Unit tests added
• System tests added

Possible Discussion Points

• KeyCloak User<->Role Mapping Thoughts
• Column name. It's currently realm_roles. It looks like internally there might also be other role types as well as groups. If/when we expose these I didn't want to have overlap. Please let me know if you have any suggestions on naming.

Notes

• I have a simple dynamic network ae5 mock which is usable for the integration tests I wrote. I am however also running into issues getting this to work as expected when run through the GitHub Action. I've pulled this out for now and will introduce it later once I have the issues ironed out.
• There is opportunity to split the test suites up (unit/integration/system) but did not want to introduce a large amount of change in this PR. I'll do this separately.

[joshburt]

After some discussions this morning around how we expose KeyCloak, I was able to access the other endpoints mentioned in option 2 for the PR. I'm going to continue down the route of Option 2 (less network calls) and update the PR shortly with the enhancements.

[jlstevens]

Looks good to me so far!

[joshburt]

Checking in to see if anyone had any feedback on this? I'd like to get updates in and a build out. :)

[mcg1969]

I don't have a strong desire to monitor you closely here. If what you're adding is strictly additive or minor, and others are giving it a thumbs up, I say go for it.

[joshburt]

Sounds good! Thank you!