features module (vods + schedule)

[liviaUeno]

Pull Request Checklist

What this PR does

Three related modules (room features) that ended up on the same branch due to development order. Described separately below to make review easier.

1. vod_service (VOD listing, retrieval and registration)

• new module: lists and retrieves recorded streams (VODs) for a room, building Oracle Object Storage playback URLs (HLS master playlist + thumbnails)
• VODs are scoped by room_id (a VOD belongs to a room); streams table migrated from channel_id → room_id
• create endpoint for registering finished recordings via a service token (for the recording pipeline — Jibri/OBS/etc.)
• endpoints: list, get, create
• frontend: VOD drawer filtered by room, HLS playback via hls.js

2. room_features (per-room feature flags)

• new module: enables/disables optional features per room (room_features table)
• used to control which tabs (VODs, events) show up in each room
• toggles in the Security tab (admin)

3. schedule_service (events via Google Calendar)

• new module: events per room, each room points to a Google Calendar
• API key stays on the server (never reaches the frontend)
• frontend: events tab in the drawer

Database

• new tables: room_features, room_calendars streams
• DDL versioned in 001_init.sql

Notes

• pre-signed URLs for VODs in private rooms: TO-DO, not included
• the vod_service create endpoint exists and is tested, but there's no recording pipeline calling it yet: the actual write flow (record → upload to Oracle → call create) isn't built. Jibri (Jitsi recording) is heavy infra and its need depends on a product decision (conference recording vs broadcast), still pending. For now VODs can only be created manually (curl/script).