[bulk] Performance and stability optimizations

## From Adobe JIRA (MWPW-183197)

### Performance Benchmarks

1. Publishing Speed: Must support publishing 20,000 files in ≤ 5 minutes.
Reference: Bacom lead recently reported publishing 14,686 files in 4 minutes 14 seconds using this bulk publisher: https://main--da-bacom--adobecom.aem.page/tools/bulk
Delete Preview & Unpublish Speed: Target faster execution for smaller batches (typically ≤ 1,000 files) due to launch-day redirect dependencies.

### Error Handling

Invalid URLs: Must be skipped automatically without halting or slowing down the job.
When URLs are input in dialog, bulk publish tool will alert there are invalid URLs present ahead of job initiation.
Reporting: A summary report should be generated post-job listing all skipped/invalid URLs.

### Functional Scope
Bulk Publish: Consolidate existing tools into one interface.
Delete Preview: Include streamlined options for deleting preview files (e.g., aem.page).
Unpublish: Include streamlined options for unpublishing live content.

## From @auniverseaway
We need to make the DA bulk operations tool more robust. Top of mind:

1. Better feedback of malformed URLs (see Loc UI) - Make sure to notify user up front of any malformed URLs on URL input
2. Support for "sync" preview bulk operations against AEM API.
3. Support for "async" publish bulk operations against AEM API.
4. Report on both sync and async operations as necessary.
5. For preview, we may even want to batch in 500 URL increments so we can give the user more immediate feedback on the job.
6. Look into DELETE speed

No files or tests are named. Start by locating the bulk operations tool and its existing publish, preview-delete, and unpublish flows, then review how it calls the AEM API. Done means malformed URLs are reported before execution, sync and async operations provide appropriate reports, and the stated performance targets are met.

Written by the indexing model from the issue text.