Refactor audio handling and S3 integration in LMS service

- Removed company-specific template rules from template application logic.
- Enhanced question generation queries to support both 'imported-mysql' and 'imported-material' sources.
- Introduced S3 audio storage functionality, including client setup and audio key generation.
- Updated audio response evaluation to store audio files in S3 or fallback to DB.
- Added new API routes for asset ingestion and ZIP import in CMS service.
- Implemented role-based access control for audio responses in LMS service.
- Created a smoke test script for validating audio roles and permissions.
- Updated frontend to support course selection in audio evaluations.

services/cms-service/src/main.rs

@@ -239,6 +239,11 @@ async fn main() {
         .route("/api/ai/review-text", post(handlers::review_text))
         .route("/api/assets", get(handlers_assets::list_assets))
         .route("/api/assets/upload", post(handlers_assets::upload_asset))
+        .route("/api/assets/import-zip", post(handlers_assets::import_assets_zip))
+        .route(
+            "/api/assets/{id}/ingest-rag",
+            post(handlers_assets::ingest_asset_for_rag),
+        )
         .route("/api/assets/{id}", delete(handlers_assets::delete_asset))
         .layer(DefaultBodyLimit::disable())
 /*