Update or create pass marks

Update existing pass mark configuration or create new one if none exists (upsert operation). Use Cases:

• Update pass mark thresholds: Modify existing O-Level and A-Level pass marks
• Initial configuration: Create pass marks if none exist
• Academic policy changes: Update pass requirements for new academic year
• System reconfiguration: Change pass mark standards Upsert Behavior: The endpoint automatically determines whether to update or create:
• If configuration exists: Performs partial update (PATCH-like behavior)
• If no configuration exists: Creates new configuration
• Returns appropriate status code (200 for update, 201 for create)
• Response includes action field indicating operation performed Request Body: Accepts partial data for updates:
• o_level: Pass mark for O-Level (0-100) - Optional
• a_level: Pass mark for A-Level (0-100) - Optional
• Can update one or both fields Singleton Pattern:
• Only one pass mark configuration exists in the system
• Uses .first() to check for existing configuration
• Automatically handles create vs update logic Validation:
• Pass marks must be valid numbers (typically 0-100)
• Validation errors are caught and returned with 400 status
• Server errors are caught and returned with 500 status