Hyperion: Course-scoped feature gating (admin-only rollout)

[FelixTJDietrich]

Problem
We need a safe, course-by-course rollout of Hyperion (exercise creation assistance) features without exposing them globally.

Outcome
Admins can enable Hyperion per course; when disabled, Hyperion UI and APIs are inaccessible for that course.

Primary flows

1. Admin enables Hyperion in Course Settings → Hyperion features appear to instructors in that course.
2. Admin disables → all Hyperion UI disappears; API calls are rejected for that course.

Acceptance criteria

• Course settings has an "Exercise Creation Assistance Enabled" toggle (only visible as an admin)
• When a course is disabled, Hyperion UI elements do not render anywhere in that course.
• All Hyperion API endpoints return 403/feature-not-enabled (or equivalent) for disabled courses.

Open questions

Do we need per-feature sub-flags, or a single course-level gate for now?

[FelixTJDietrich]

The rollout will happen via activation of the hyperion profile for now, if it is active then any instructor can use it and it is not hidden behind configuration which hopefully leads to better discoverability and usage