Feat: Add Confirmation Dialog for Global Face Reclustering

[Cubix33]

Describe the feature

🌟 Feature Description

I propose adding a Confirmation Dialog (or Alert Modal) that appears when a user clicks the "Recluster Faces" button in the Settings > Application Controls section.

Currently, clicking the "Recluster Faces" button immediately triggers the triggerGlobalReclustering mutation. Since this is a resource-intensive operation that rebuilds face clusters from scratch, users should be warned about the consequences and asked to confirm their intent before the process begins.

🔍 Problem Statement

1. No Safety Net: There is no intermediate step. A single click initiates a heavy backend process.
2. User Frustration: An accidental click could consume system resources or alter data organization unexpectedly, with no obvious way to cancel.

🎯 Expected Outcome

1. Interaction Update: Clicking "Recluster Faces" should not immediately call the API.
2. UI Feedback: A modal/dialog should appear with a warning message:
   • Title: "Start Global Reclustering?"
   • Message: "This process will rebuild all face clusters from scratch. It may take a significant amount of time and system resources. Are you sure you want to continue?"
3. Action:
   • Cancel: Closes the dialog; no action taken.
   • Confirm: Closes dialog and triggers reclusterMutation.mutate().

🛠 Proposed Implementation

Modify ApplicationControlsCard.tsx to include a state for the dialog visibility and wrap the mutation trigger.

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I want to work on this issue

[github-actions]

👋 Thanks for opening this issue! The maintainers will review it shortly. Till then, do not open any PR. This is a strict rule we like to follow around here :)

[Soumojit-007]

This looks like a solid UX and safety improvement, especially given how resource-intensive global face reclustering is. Nice catch, @Cubix33. Adding a confirmation step before triggering the mutation makes a lot of sense here. Once the maintainers approve, I’d be happy to help this could be approached by gating the existing reclustering trigger behind a lightweight confirmation dialog at the UI level so the action only proceeds after explicit user consent. Glad to assist or review if needed.