[Due for payment 2026-02-04] Refactor ConfirmModal usage to useConfirmModal in Report and Home 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:

ReportDetailsExportPage.tsx
PureReportActionItem.tsx
PopoverReportActionContextMenu.tsx
HeaderView.tsx
FloatingActionButtonAndPopover.tsx
ReportDetailsPage.tsx
ReportParticipantsPage.tsx
RoomMembersPage.tsx
RoomMemberDetailsPage.tsx
ReportParticipantDetailsPage.tsx
EditReportFieldPage.tsx
TravelTerms.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 @brianlee-expensify (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 would like to work on this.

[roryabraham]

@mohammadjafarinejad giving this one to @abbasifaizan70 since you were assigned to #76696