Create a Recall.ai bot that joins a live meeting and records it (regions, auth, POST /bot)

Documented steps

1. Pick your Recall.ai region base URL: https://us-east-1.recall.ai, https://us-west-2.recall.ai, https://eu-central-1.recall.ai, or https://ap-northeast-1.recall.ai. Bots, recordings and API keys are region-local; a bot created in one region 404s in another. Legacy host api.recall.ai aliases us-east-1. Ref: https://docs.recall.ai/docs/regions
2. Create an API key in the region-specific dashboard (e.g. https://us-east-1.recall.ai/dashboard/developers/api-keys). Keys do not auto-expire; rotate by disabling and re-issuing. Ref: https://docs.recall.ai/reference/authentication
3. Send 'Authorization: Token <RECALLAI_API_KEY>' and 'Content-Type: application/json' on every request. The reference describes the 'Token ' prefix as optional but every working example includes it - always send it.
4. POST https://<region>.recall.ai/api/v1/bot/ with body {"meeting_url": "<zoom/meet/teams url>", "bot_name": "My Bot", "recording_config": {"transcript": {"provider": {"recallai_streaming": {}}}}}. bot_name is optional (default 'Meeting Notetaker', 1-100 chars). Ref: https://docs.recall.ai/reference/bot_create
5. For production, set join_at (ISO 8601) at least 10 minutes in the future: those are 'scheduled' bots with a reserved machine and guaranteed join. Bots created with less notice are 'ad-hoc', drawn from a limited warm pool, and can return HTTP 507 with Retry-After during demand spikes. Ref: https://docs.recall.ai/docs/creating-and-scheduling-bots
6. Zoom: no special bot config needed, but waiting-room meetings require host admission; Zoom webinars, Zoom Gov, Zoom Rooms, VDI and Video SDK sessions are unsupported. Ref: https://docs.recall.ai/docs/zoom-overview
7. Google Meet: an unauthenticated bot needs a Workspace member to click 'Let in'; authenticated bots skip that but still honor waiting-room settings. Livestreams and breakout rooms are unsupported. Ref: https://docs.recall.ai/docs/google-meet
8. Microsoft Teams: bots are normally admitted from the lobby unless org settings allow direct entry; registration-required meetings, webinars, Live Events/Town Halls, direct calls and breakout rooms are unsupported. Ref: https://docs.recall.ai/docs/microsoft-teams
9. On success you get HTTP 201 with the bot object; persist bot.id (UUID, region-scoped) for every later status/media call.
10. Track lifecycle via status change events: joining_call -> (in_waiting_room) -> in_call_not_recording -> recording_permission_allowed -> in_call_recording -> call_ended -> done, with a 'fatal' short-circuit path. Ref: https://docs.recall.ai/docs/bot-status-change-events
11. Handle HTTP 429 (rate limited) and 507 (no ad-hoc bots available) with exponential backoff honoring Retry-After. Ref: https://docs.recall.ai/reference/errors