fix(tests): raise migration-boot hook timeout pins to the 120s default (#900)

The 3.97.0-beta.0 release PR (#899) failed its backend Tests job on
slideshowPublic.test.js: bootCrmDb's full migration chain crossed the
suite's explicit 30s beforeAll timeout argument on a slow runner. #860
raised the config default and the jest.setTimeout pins to 120s, but
hook-ARGUMENT pins override the config default and were left behind —
same time-bomb, different syntax.

Every beforeAll that boots the migration chain and pinned 30s/60s is
raised to 120000 (16 suites). Untouched on purpose: the three suites
whose pinned hooks don't run migrations (webhookDelivery,
imageProcessor.storage, storageBackend) and publicQuotes' 30s pin on
the rate-limit lockout test — neither grows with the migration chain.

No test logic changed.

Co-authored-by: Paul Nothaft <[email protected]>

backend/__tests__/routes/adminEventQr.test.js

@@ -105,7 +105,7 @@ describe('admin event QR endpoints', () => {
     expect(res.status).toBe(200);
     expect(res.headers['content-type']).toBe('application/pdf');
     expect(res.body.slice(0, 4).toString()).toBe('%PDF');
-  }, 30000);
+  }, 120000);
 
   it('409s when the event has no share link', async () => {
     // events.share_link is NOT NULL — an empty string is the closest real-world