[$750] Refactor ConfirmModal usage to useConfirmModal in settings and profile pages

[roryabraham]

Coming from #68799 (comment)...

Problem

When every component mounts its own ConfirmModal in the component tree, it creates component bloat, memory overhead from multiple modal instances, and repetitive boilerplate code that makes the application harder to maintain.

Solution

Refactor ConfirmModal usage to useConfirmModal in the following files:

TroubleshootPage.tsx
CardSection.tsx
SecuritySettingsPage.tsx
CloseAccountPage.tsx
TwoFactorAuth/DisablePage.tsx
TwoFactorAuth/EnabledPage.tsx
LockAccountPage.tsx
InitialSettingsPage.tsx
ConsolePage.tsx
VacationDelegatePage.tsx
ContactMethodDetailsPage.tsx
WalletPage.tsx
VisibilityPage.tsx

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021996470600213306769
• Upwork Job ID: 1996470600213306769
• Last Price Increase: 2026-03-26
• Automatic offers:
• truph01 | Contributor | 109701642

Issue Owner

Current Issue Owner: @

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021996470600213306769

[melvin-bot]

Current assignee @ZhenjaHorbach is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[truph01]

I can work on it as implementor

[abbasifaizan70]

I would like to work on this.