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/parks/models/parks.py

@@ -13,7 +13,6 @@ if TYPE_CHECKING:
 
 @pghistory.track()
 class Park(TrackedModel):
-
     # Import managers
     from ..managers import ParkManager
 
@@ -226,7 +225,8 @@ class Park(TrackedModel):
             if historical:
                 print(
                     f"Found historical slug record for object_id: {
-                        historical.object_id}"
+                        historical.object_id
+                    }"
                 )
                 try:
                     park = cls.objects.get(pk=historical.object_id)
@@ -250,7 +250,8 @@ class Park(TrackedModel):
             if historical_event:
                 print(
                     f"Found pghistory event for pgh_obj_id: {
-                        historical_event.pgh_obj_id}"
+                        historical_event.pgh_obj_id
+                    }"
                 )
                 try:
                     park = cls.objects.get(pk=historical_event.pgh_obj_id)