fix job-queue e2e test: use toMatchObject for payload assertions

The add_job SQL function now includes actor_id in the returned payload.
Using toMatchObject instead of toEqual allows the test to pass with
additional fields without breaking on upstream schema changes.

Author: Anmol1696

tests/e2e/__tests__/job-queue.test.ts

@@ -61,7 +61,7 @@ describe('SQL: Job Queue (k8s)', () => {
       expect(job).toBeDefined();
       expect(job.id).toBeDefined();
       expect(job.task_identifier).toBe(`${TEST_PREFIX}-basic`);
-      expect(job.payload).toEqual({ message: 'hello from test' });
+      expect(job.payload).toMatchObject({ message: 'hello from test' });
       expect(job.attempts).toBe(0);
       expect(job.locked_by).toBeNull();
     });
@@ -75,7 +75,7 @@ describe('SQL: Job Queue (k8s)', () => {
 
       expect(retrieved).toBeDefined();
       expect(retrieved!.id).toBe(created.id);
-      expect(retrieved!.payload).toEqual({ key: 'value' });
+      expect(retrieved!.payload).toMatchObject({ key: 'value' });
     });
   });
 });