Add operators and property owners functionality

- Implemented OperatorListView and OperatorDetailView for managing operators.
- Created corresponding templates for operator listing and detail views.
- Added PropertyOwnerListView and PropertyOwnerDetailView for managing property owners.
- Developed templates for property owner listing and detail views.
- Established relationships between parks and operators, and parks and property owners in the models.
- Created migrations to reflect the new relationships and fields in the database.
- Added admin interfaces for PropertyOwner management.
- Implemented tests for operators and property owners.

parks/models.py

@@ -7,7 +7,8 @@ from decimal import Decimal, ROUND_DOWN, InvalidOperation
 from typing import Tuple, Optional, Any, TYPE_CHECKING
 import pghistory
 
-from companies.models import Company
+from operators.models import Operator
+from property_owners.models import PropertyOwner
 from media.models import Photo
 from history_tracking.models import TrackedModel
 from location.models import Location
@@ -54,8 +55,11 @@ class Park(TrackedModel):
     coaster_count = models.IntegerField(null=True, blank=True)
 
     # Relationships
-    owner = models.ForeignKey(
-        Company, on_delete=models.SET_NULL, null=True, blank=True, related_name="parks"
+    operator = models.ForeignKey(
+        Operator, on_delete=models.SET_NULL, null=True, blank=True, related_name="parks"
+    )
+    property_owner = models.ForeignKey(
+        PropertyOwner, on_delete=models.SET_NULL, null=True, blank=True, related_name="owned_parks"
     )
     photos = GenericRelation(Photo, related_query_name="park")
     areas: models.Manager['ParkArea']  # Type hint for reverse relation