Fix PostgreSQL index name collision in MigrationQueueIndexOptimization

The migration was creating an index named 'workerkey' on the queued_jobs
table, but this name already exists on the queue_processes table (created
in MigrationQueueInitV8).

PostgreSQL requires index names to be unique across the entire schema,
unlike MySQL which only requires uniqueness within a table. This caused
the migration to fail with error:

SQLSTATE[42P07]: Duplicate table: 7 ERROR: relation "workerkey" already exists

Solution: Rename the index from 'workerkey' to 'queued_jobs_workerkey'
to follow the table_column naming convention and avoid the collision.

This fix is backwards compatible with MySQL and resolves the PostgreSQL
migration failure.

Author: jdd-canada

config/Migrations/20251119005411_MigrationQueueIndexOptimization.php

@@ -42,7 +42,7 @@ public function change(): void {
 			->addIndex(
 				['workerkey'],
 				[
-					'name' => 'workerkey',
+					'name' => 'queued_jobs_workerkey',
 				],
 			)
 			->update();