Query project logs via the Supabase Management API (logs.all endpoint removed -> use logs)

Documented steps

1. BREAKING CHANGE: The Supabase Management API logs.all endpoint (GET /projects/{ref}/analytics/endpoints/logs.all) is being REMOVED on 23 September 2026 for all projects, with no backcompat. Migrate any script, integration, or tooling that calls logs.all before then.
2. Change the endpoint path from analytics/endpoints/logs.all to analytics/endpoints/logs. Auth is unchanged (Management API key).
3. Convert your query SQL to the ClickHouse dialect: the new logs endpoint only accepts ClickHouse SQL, not Postgres SQL.
4. All log sources now live in a single unified 'logs' table instead of one table per source. Filter to a specific source in the WHERE clause with source_name. Before: SELECT timestamp, event_message FROM edge_logs ORDER BY timestamp DESC LIMIT 100. After: SELECT timestamp, event_message FROM logs WHERE source_name = 'edge_logs' ORDER BY timestamp DESC LIMIT 100.
5. Nested fields moved from the metadata array to a flat log_attributes map. Stop using one CROSS JOIN unnest() per nesting level; read fields directly with map key access, e.g. log_attributes['request.method'].