Barista should be able to pick up groups changes as it picks up users changes

[kltm]

As it currently stands, refresh user functions pick up new user identity/session information, but does not do so for groups, which requires a restart. To get updated groups.yaml information into the production server, Barista should be updated along the lines of what it does with users.yaml, so that user queries can return their groups as well.

[kltm]

This is from issue exploration with @ukemi earlier today.

To clarify, while displayed in noctua, noctua has no direct access to the groups file, and must ask barista when getting user info.

[kltm]

...digging into the code a little...how does this not work?

[kltm]

Well, it was essentially tied to #569