Improve efficiency of API calls

[blms]

• More efficient auth callbacks
• Pool together groups reqs instead of hitting /api/groups a bunch
• Pool together name reqs instead of hitting /api/user a bunch
• Better caching

[blms]

We should only need to hit the auth endpoints when the user session object needs to be updated. The user object contains:

{
  id: '1',
  name: 'Test User',
  firstName: 'Test',
  lastName: 'User',
  email: 'test@email.com',
  affiliation: 'Jest Tests',
  groups: [{
    id: 'abcd1234', name: 'Test Group', ownerName: 'Test User', memberCount: 2, role: 'owner',
  }],
  createdAt: '2881-10-05T14:48:00.000',
  updatedAt: '2881-10-05T14:48:00.000',
};

So we need to update the session object when:

• User changes their name or affiliation
• User joins a group
• User added to a group
• User leaves a group
• User is removed from a group
• User's role in a group changes
• Group changes its name
• Group membership number changes
• Group is deleted

Otherwise we don't need to make an API query to update the user object, we can just store it from login or whatever was the last change. We just need to make sure that the user object we're using everywhere is consistent and retains any updates made since login.