feat(ci): materialize CI runs and jobs off github-actions traces - #1718

🟢 Confidence 10/10 · safe to merge
No findings; the only unverified piece is the backfill's (TraceId, SpanId) NOT IN (...) subquery, the repo's first tuple subquery, proven only by the new ClickHouse e2e.
_{no findings · tests covered · risk medium · 1/1 new units observable}

Adds migration 0047: ci_runs and ci_jobs, two one-row-per-run/job projections of github-actions traces with their views and a deduplicating backfill, plus the Tinybird datasources, local schema v38 and catalog notes. Nothing reads them yet; safe to merge. The Warehouse*Error issues whose frames land in packages/query-engine/src/ch/tables.ts are unrelated: the diff only adds two table exports and no query path, so it neither causes nor fixes them.

• Migration 0047 creates ci_runs, ci_jobs and their views, then backfills retained traces skipping rows already stored
• ciRuns/ciJobs Tinybird datasources and MVs extract the cicd.* attributes into columns, 365-day TTL
• Local schema bumps to v38 via an additive, forward-filled step; scoped delete gets unkeyed plans

Before merge

• Migration · Check it is safe on production data and with the code still deployed · packages/domain/src/clickhouse/migrations/0047_ci_runs_jobs.ts
• Warehouse · Deploy the schema before the code that reads it · packages/domain/src/tinybird/datasources.ts

Production impact

_{4e74953 · Updated on every push. Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.}