feat: add maintainer analytics trends

[saurabhhhcodes]

Summary

• adds 12-week weekly merge-rate and XP-distributed trend charts to /maintainer
• adds a 6-month stacked L0/L1/L2/L3+ contributor level distribution chart
• scopes analytics to the selected maintainer installation repositories and caches the compact chart payload for 30 minutes
• adds a Supabase SQL aggregation function so the page receives aggregated JSON instead of raw PR/recommendation/profile rows

Performance notes

The heavy aggregation is done in Postgres via maintainer_analytics_trends(repo_names text[], as_of timestamptz default now()).

EXPLAIN ANALYZE query used for review:

explain analyze
select maintainer_analytics_trends(array['demo/sample-repo']::text[]);

The query is bounded to 12 weeks for weekly PR/XP trends and 6 months for level distribution snapshots. It filters by repo_full_name = any(repo_names) and uses existing indexed tables/columns around pull_requests.repo_full_name, pull_requests.state, recommendation issue joins, and profile/level-up lookups. The function returns one JSON payload, so the route avoids shipping raw event rows to React.

Tests

• npm run test -- src/lib/maintainer/analytics.test.ts
• npm run lint -- --file 'src/app/(app)/maintainer/page.tsx' --file 'src/app/(app)/maintainer/analytics-trends.tsx' --file src/app/actions/maintainer.ts --file src/lib/maintainer/analytics.ts
• npm run typecheck
• npm run build passes; existing unrelated warnings remain in src/app/(app)/dashboard/sync-button.tsx, src/app/(app)/issues/issues-list.tsx, and metadataBase.

Closes #92

[vercel]

@saurabhhhcodes is attempting to deploy a commit to the codersogs-3057's projects Team on Vercel.

A member of the Team first needs to authorize it.

[saurabhhhcodes]

Thanks again for assigning #92. I kept this scoped to the maintainer analytics page and moved the aggregation into Postgres so the UI only receives compact chart data. When reviewing, could you also add the appropriate GSSoC approval / difficulty / type labels if this fits the program scoring? I included the EXPLAIN ANALYZE query in the PR body for the performance check.

[saurabhhhcodes]

Synced this branch with the latest main in commit cbaffd0; the maintainer analytics changes merged cleanly with the new upstream dashboard/maintenance updates.

Validation after the sync:

• ./node_modules/.bin/tsc --noEmit passed
• ./node_modules/.bin/prettier --check src/app/\(app\)/maintainer/analytics-trends.tsx src/app/\(app\)/maintainer/page.tsx src/app/actions/maintainer.ts src/lib/maintainer/analytics.ts src/lib/maintainer/analytics.test.ts supabase/migrations/0012_maintainer_analytics_trends.sql passed
• git diff --check origin/main...HEAD passed

I also retried ./node_modules/.bin/vitest run src/lib/maintainer/analytics.test.ts, but this local macOS runtime still fails before tests load due the Rollup optional native package/code-signing issue for @rollup/rollup-darwin-arm64. No analytics code failure was reached.