Queue imports for a connection's recent Google Meet conferences
Context
Tenth PR of the Google Meet app, following #30587 (app shell), #30588 (test setup), #30589 (Google OAuth connection), #30590 (Meet API client), #30591 (listing), #30592 (transcript mapping), #30593 (calendar event matching), #30595 (Call Recording write and role) and #30597 (import of one conference). The app will import Google Meet recordings, transcripts and Gemini notes into Call Recordings, the same way the Teams, Fathom and Granola apps do. The full sequence of PRs is listed in #30587.
#30597 added the job that imports one conference. This PR adds the job that finds which conferences to import for one connection. Nothing schedules it yet: the hourly run over all connections comes in the next PR.
What this PR does
google-meet-queue-conference-imports: a logic function meant to run as a background job for one connection. It lists the conferences the connected account started in the last six hours, keeps the ones that have ended, and queues onegoogle-meet-import-conferencejob per conference. Ongoing conferences are left for a later run.buildGoogleMeetConferenceImportJob: builds the payload and the job id of an import. The id combines the conference's Call Recording id with the current hour, so queueing the same conference twice within an hour starts one run, while a later hour imports it again and picks up a transcript Google published late.enqueueGoogleMeetConferenceImportsOrThrow: queues the import jobs in batches of 200, the mostenqueueJobsaccepts per call.chunkIntoBatches: same helper as the Teams app, with an object argument.
Splitting discovery and import into separate jobs follows the background jobs guide: each run gets its own timeout, and one failing conference does not fail the others.
Checks
Run locally in the app folder: yarn install --immutable, yarn lint, yarn typecheck, yarn test:unit (66 tests), the repo formatter and twenty app build pass, and the built manifest contains both logic functions. The unit tests mock the SDK and the Meet client; the jobs have not been run on a live workspace yet. The integration test needs a running server and was not run locally; CI runs it.