List Google Meet transcripts, entries and participants
Context
Fifth PR of the Google Meet app, following #30587 (app shell), #30588 (test setup), #30589 (Google OAuth connection) and #30590 (Meet API client). 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.
This one adds the remaining read calls the transcript import needs. Nothing calls them yet: the import in a following PR is their first user.
What this PR does
listGoogleMeetCollection: one paginated list helper for the Meet API. It followsnextPageTokenwith a page limit and reads the items under the collection key each endpoint uses.listGoogleMeetConferenceRecordsnow uses it instead of its own pagination.listGoogleMeetTranscripts,listGoogleMeetTranscriptEntriesandlistGoogleMeetParticipants, with the resource types from the Meet REST API v2 reference.buildGoogleMeetUrlOrThrow(renamed frombuildGoogleMeetUrl) now refuses a resource path that resolves outsidehttps://meet.googleapis.com/v2/. Resource names such asconferenceRecords/{id}are interpolated into the path, so a name containing..cannot redirect the access token to another endpoint.- The page size and page limit constants are no longer specific to conference records.
Request and response shapes come from the reference pages for transcripts.list, transcripts.entries.list and participants.list.
Checks
Run locally in the app folder: yarn install --immutable, yarn lint, yarn typecheck, yarn test:unit (20 tests) and the repo formatter pass. The unit tests mock fetch; this code has not been run against the real Meet API yet.