Add migrations for ParkPhoto and RidePhoto models with associated events

- Created ParkPhoto and ParkPhotoEvent models in the parks app, including fields for image, caption, alt text, and relationships to the Park model.
- Implemented triggers for insert and update operations on ParkPhoto to log changes in ParkPhotoEvent.
- Created RidePhoto and RidePhotoEvent models in the rides app, with similar structure and functionality as ParkPhoto.
- Added fields for photo type in RidePhoto and implemented corresponding triggers for logging changes.
- Established necessary indexes and unique constraints for both models to ensure data integrity and optimize queries.

backend/apps/email_service/services.py

@@ -34,9 +34,7 @@ class EmailService:
 
             # Use provided from_email or construct from config
             if not from_email:
-                from_email = f"{
-                    email_config.from_name} <{
-                    email_config.from_email}>"
+                from_email = f"{email_config.from_name} <{email_config.from_email}>"
             elif "<" not in from_email:
                 # If from_email is provided but doesn't include a name, add the
                 # configured name
@@ -101,8 +99,9 @@ class EmailService:
             if response.status_code != 200:
                 error_message = response.text if response.text else "Unknown error"
                 raise Exception(
-                    f"Failed to send email (Status {
-                        response.status_code}): {error_message}"
+                    f"Failed to send email (Status {response.status_code}): {
+                        error_message
+                    }"
                 )
 
             return response.json()