feat: residents PR 2

[CK-7vn]

Pre-Submission PR Checklist

• No debug/console/fmt.Println statements
• Unnecessary development comments removed
• All acceptance criteria verified
• Functions according to ticket specifications
• Tested manually where applicable
• Branch rebased with latest main
• No business logic exists within the database layer

Description of the change

Pull-Requests for Residents 2
Adds per-row action buttons (Edit, Reset Password, dropdown menu) and six dialog components for managing individual residents: Edit Profile, Reset Password (confirm + result with copy), Deactivate Account, Delete Resident, and Transfer Resident (DA only).
Deactivated residents show "No actions available" with all action buttons hidden.

New file: frontend-v2/src/components/residents/ResidentModals.tsx
Modified: frontend-v2/src/pages/admin/StudentManagement.tsx, frontend-v2/src/types/user.ts, backend/src/database/users.go

Requirements

Edit Resident

• 359: Edit button opens edit dialog
• 360: Save updates resident information
• 361: Successful edit shows toast notification
• 389: All fields are editable
• 392: Cancel discards changes
• 393: Dialog pre-populates with resident data
• 669: Edit Profile button hidden for deactivated

Reset Password

• 369: Reset password button opens confirmation
• 372: Success toast displays after reset
• 375: Reset generates temporary password
• 395: Copied state shows checkmark temporarily
• 400: Confirmation dialog explains temporary password
• 401: Copy button copies password to clipboard
• 670: Reset Password button hidden for deactivated

Deactivate Account

• 410: Deactivate option in action menu
• 411: Deactivate dialog opens with warning
• 412: Deactivate lists consequences
• 413: Deactivate requires typing Resident ID
• 414: Submit disabled until ID matches
• 419: Deactivated badge appears after action
• 421: Success toast after deactivation

Delete Resident

• 390: Successful deletion shows toast
• 391: Submit button uses destructive styling
• 394: Submit disabled until ID matches exactly
• 415: Delete option in action menu
• 416: Delete dialog opens with warning
• 417: Delete warns action cannot be undone
• 418: Delete requires typing Resident ID
• 420: Success toast after deletion

Transfer Resident (DA only)

• 135: Transfer disabled for deactivated residents
• 136: Transfer Resident option appears for DA
• 137: Transfer requires typing Resident ID to confirm
• 184: Submit disabled until ID matches
• 422: Transfer dialog opens
• 423: Shows current facility
• 424: Facility dropdown excludes current
• 425: Unenrollment warning displayed
• 426: Program conflicts listed
• 427: What happens next section
• 428: ID confirmation input
• 429: Transfer calls API
• 430: Success toast after transfer
• 431: Resident list refreshes after transfer

Action Menu

• 671: Action dropdown menu hidden for deactivated

Screenshot(s)

This PR

Redesign

Additional context

• Backend: Added Preload("Facility") to GetCurrentUsers so facility data is available in list responses
• Frontend: Added facility_id to TypeScript User type to match Go backend response; TransferDialog falls back to facilities list lookup if nested facility object is missing
• Username field is intentionally disabled (read-only) in the Edit dialog

[carddev81]

Findings:

Fac/Dept Admin

1. Missing tooltips on action icons.
2. Need more gap between buttons and Resident ID text field on Edit Resident Profile
3. Figma allows edit of username
4. Incorrect color of toast when password reset and not in correct location
5. Incorrect color of toast when editing a user and not in correct location (fix all action toasts)
6. Incorrect bullets type on Deactivate account modal---this is displaying hyphens
7. Incorrect icon for Transfer resident.
8. Transfer Resident Modal Programs 'not available' list showing program name and class name, per Figma only show the program name.

[CK-7vn]

1. Done.
2. done
3. We don't actually allow editing of usernames in the backend. I noted in the initial PR comment that I chose not to include it on purpose. I don't think this functionality adds value personally and I don't think admins will be very happy getting a million requests to change usernames so I don't foresee it actually being used.
4. done
5. done
6. done
7. done
8. done

[carddev81]

1. Done.
2. done
3. We don't actually allow editing of usernames in the backend. I noted in the initial PR comment that I chose not to include it on purpose. I don't think this functionality adds value personally and I don't think admins will be very happy getting a million requests to change usernames so I don't foresee it actually being used.
4. done
5. done
6. done
7. done
8. done

@calisio I believe you coded the figma to allow editing a username on purpose where the username can be updated now? I thought maybe you brought this up in a meeting? Can you confirm whether or not this is wanted before we proceed with this PR.

[carddev81]

1. Tooltips exist now, but they don't match figma
2. Need more gap between buttons and Resident ID text field on Edit Resident Profile (previous issue)

current:

target:

3. Toasts are located at the bottom but toast messages don't match figma

[carddev81]

Looks/Tests good