[FEAT] CD: Asynchronous Folder Move/Copy Handling with UI

Feature Title

CD: Asynchronous Folder Move/Copy Handling with UI

Problem

When a user moves or copies a folder containing a large number of files, the UI should not block the user from multitasking while the move/copy operation completes.

Goal

By supporting asynchronous move/copy actions for folders the users will be able to multitask and continue using dotcms while the move/copy operation completes thus making our users more efficient.
Ensure a responsive and non-blocking user experience when moving or copying folders containing a large number of assets. Implement asynchronous processing and a dedicated UI to monitor the progress and status of these operations. This prevents the main Content Drive interface from freezing during long-running folder operations.

Personas

• Developer teams
• Content teams
• DevOps teams
• Sys Admin

Demo Expectations

[Describe exactly what someone can show in a bi-weekly demo to prove the value is delivered]

Success Criteria

• Moving and copying folders containing a large number of assets is processed asynchronously.
• A progress UI is displayed during folder move/copy operations.
• The progress UI displays:
  • The name of the folder being moved/copied.
  • Overall progress (%).
  • The number of assets processed.
  • Status (copying/moving, completed, failed).
• User can cancel the ongoing folder move/copy operation.
• Success and error messages are displayed upon completion of the operation.
• The user interface provides feedback on:
  • The number of assets moved/copied.
  • The number of assets that failed to move/copy (with error details).

Demo Expectations

• Demonstrate moving or copying a folder containing a significant number of assets (e.g., 50+ files and subfolders).
• Show the progress UI with real-time updates on the overall progress, assets processed, and status.
• Demonstrate the ability to cancel the move/copy operation.
• Show success and error messages appearing upon completion, along with details of any files that failed.
• Verify that folder operations respects user permissions

Start by tracing the existing folder move/copy flow across the Content Drive UI and server-side operation; the issue names no files or tests. Compare the current flow with the success criteria, then identify how progress, cancellation, permissions, and failure details should be represented. Done means large folder operations are non-blocking and the UI demonstrates progress, completion, cancellation, and errors.