Refactor user read page into categorized split-table layout

[somethingnew2-0]

Summary

• Reorganizes the user read page from two flat tables (Owner of Groups/Roles, Member of Groups/Roles) into three sections by group type: Access Roles, App Groups, and Standard Groups
• Each section shows side-by-side Ownerships and Memberships tables, replacing the previous separate full-width tables
• App Groups are further sub-grouped by app, with clickable app name headers linking to /apps/{appName}
• Sections are hidden when both ownerships and memberships are empty for that type
• Replaces the duplicated OwnerTable/MemberTable components with a single unified GroupTable component parameterized by an owner boolean
• Drops the Type column from tables since items are now categorized by section

[barborico]

Aesthetics look good to me. I hade Claude take a pass, and it found a but that seems legit.

[barborico]

The useCallback dep array is missing owner and user.id, both of which are captured from
props and drive the mutation body.

The old OwnerTable/MemberTable each hard-coded their API body, so the only closed-over
variable was user.id (already a pre-existing gap). The refactor adds owner as a new
closed-over prop value, making the stale-closure risk concrete: if React Query's
putGroupUsers object happens to be stable across a re-render where owner has changed,
the callback fires the wrong mutation — silently calling owners_to_remove when
members_to_remove was intended, or vice versa.

Suggested change

	+ [putGroupUsers, owner, user.id],

[somethingnew2-0]

Good catch, fixed in 0d9f38a. Agreed the deps were incomplete, worth noting the stale-closure isn't reachable, today since each , is rendered with a literal owner and a stable user.id from the route, but the fix is still correct and guards future refactors.