aerocargo/queue-manager failed jobs doesn't support UUIDs

Queue Manager assumes failed-job driver must equal database and assumes failed job keys are numeric id values. Laravel 10+ commonly uses UUID failed jobs with driver database-uuids. Because of this mismatch, failed jobs are not handled correctly and module features for failed jobs are incompatible with UUID mode. Observed Behavior * Failed job logging errors with missing uuid when driver is database and table requires uuid * Queue Manager failed-jobs UI/logic is disabled or inconsistent when failed driver is database-uuids * Retry/delete/exception operations use id-only logic and do not support uuid identifiers Expected Behavior * Queue Manager should support both failed-job drivers: * database * database-uuids * Failed jobs should be visible and manageable in both modes * Retry, delete, and exception lookup should work with id in legacy mode and uuid in UUID mode Proposed Fix * Update all failed-driver checks to accept both database and database-uuids * Introduce driver-aware failed identifier handling: * use id for database * use uuid for database-uuids * Update failed job queries, bulk actions, and exception lookup to use the correct identifier column by driver * Keep frontend payload stable by still returning a single id field, mapped from uuid in UUID mode