Refactor AIB pages: Deduplicate components and use tournament API for leaderboards

Problem

The AIB tournament pages (/aib/2024/q3 through /aib/2025/fall) are heavily duplicated. Each quarter has its own near-identical copy of every component — page-view, hero, cards, and leaderboard — with only small data differences (quarter label, start date, image URL, tournament slug). This results in ~20 files that are mostly copy-pasted, including 4 leaderboard files with ~2,300 lines of hardcoded bot ranking data.

Proposed Changes

1. Define a per-tournament config object with all the differences (quarter label, year, image URL, date/prize translation keys, tournament slug, etc.) so adding a new tournament is just a new entry.

2. Replace duplicated components with shared parameterized ones: one Hero, one Cards, one AibPageView layout, one Leaderboard — all driven by the config.

3. Replace hardcoded leaderboard data with the existing getProjectLeaderboard(projectId) API (already used by tournament pages), or simply link to the tournament page (like Fall 2025 already does). No backend changes expected — verify that older tournaments already have leaderboard data in the API.

Scope

~20 files can be collapsed into ~5 shared components + one config:

Priority

Low — cleanup/tech-debt. Ideal timing: before the next seasonal tournament ends and results need publishing.