Root cause: The validation in NotificationBaseRepository._validate_notification_data
was checking enum objects against string lists, causing validation to fail when the
EnhancedNotificationService passed NotificationType/NotificationPriority/NotificationStatus
enum objects instead of their string values.
The validation now properly handles both enum objects (by extracting their .value)
and string values, fixing the "Invalid notification type" error from orchestrator.
Changes:
- Updated priority validation to handle enum objects
- Updated notification type validation to handle enum objects
- Updated status validation to handle enum objects
Fixes the error:
"Invalid notification data: ['Invalid notification type. Must be one of: ['email', 'whatsapp', 'push', 'sms']']"
