Stop exposing credential columns through v_users_groups

public.v_users_groups is actively consumed through the Drizzle symbol vUsersGroups in src/repositories/user.ts, but the view exposes password_hash, password_reset_token, password_reset_expires_at, and email_verification_token even though the listing consumer only needs identity/profile fields plus groups. Design and implement a least-privilege replacement or narrow the view without breaking the admin user list; update Drizzle schema and callers, test the list contract, and obtain fresh environment-specific DB GO before any DEV or PROD DDL. Related Jira tracking noted in current docs: MOBAAPI-684.