[Due for payment 2026-07-29] Refactor ConfirmModal usage to useConfirmModal in various components, hooks, and providers

[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:

ImportSpreadsheet.tsx
ImportSpreadsheetConfirmModal.tsx
DotIndicatorMessage.tsx
BookTravelButton.tsx
AccountSwitcher.tsx
ExportWithDropdownMenu.tsx
LocationPermissionModal/index.tsx
LocationPermissionModal/index.desktop.tsx
ContactPermissionModal/index.native.tsx
FocusModeNotification.tsx
SupportalPermissionDeniedModalProvider.tsx
DelegateNoAccessModalProvider.tsx
LockedAccountModalProvider.tsx
useFilesValidation.tsx
useCreateEmptyReportConfirmation.tsx
src/Expensify.tsx
TransactionReceiptModalContent.tsx

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @ZhenjaHorbach

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @dylanexpensify (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.

[mohammadjafarinejad]

I'd like to work on this issue, as the solution approach is already clearly defined in the OP.

[abbasifaizan70]

I can take this .