Add the Google OAuth connection to the Google Meet app
Context
Third PR of the Google Meet app, following #30587 (app shell) and #30588 (test setup). 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.
Apps cannot use the core Gmail and Calendar connection, so the app needs its own Google OAuth connection before it can call the Meet API.
What this PR does
- Declares two OAuth connection providers that share one config, like Teams and Fathom:
google-meet(shared with the workspace) andgoogle-meet-user(personal). - Requests
openid,emailandhttps://www.googleapis.com/auth/meetings.space.readonly. The restricted Drive scope needed to download recordings and notes is left for the PR that uses it. - Adds the
GOOGLE_CLIENT_IDandGOOGLE_CLIENT_SECRETserver variables that hold the OAuth client of the Twenty server. - Sends
access_type=offlineandprompt=consent, which Google requires to return a refresh token, and sets Google's revocation endpoint so disconnecting revokes the token. - Replaces the install check in the integration test with one asserting both providers are registered with the Meet scope and no configured credentials (same shape as the Teams test).
Endpoints come from Google's OpenID discovery document (https://accounts.google.com/.well-known/openid-configuration), which also lists S256 PKCE support.
No logic function uses the connection yet, so this adds no runtime behaviour beyond the providers appearing in the app settings.
Checks
Run locally in the app folder: yarn install --immutable, yarn lint, yarn typecheck, yarn test:unit and twenty app build pass, and the built manifest contains both providers. The integration test needs a running server and was not run locally; CI runs it. The OAuth flow itself has not been exercised against Google yet.