feat(ticket): implement ticket generation policies and validity time management

- Added `ticket_generation_policy` column to `catalog_items` table to manage ticket generation strategies.
- Created `ticket_validity_times` table to allow multiple validity times per ticket.
- Introduced `validity_time_id` column in `event_dates` table to associate event dates with validity times.
- Established `ticket_validity_groups` and `ticket_validity_group_times` tables to group validity times for tickets.
- Updated seeder to set default ticket generation policy for specific tenant.
- Enhanced tests to cover new functionality, including ticket generation based on event dates and validity times.
- Refactored ticket validity checks to accommodate multiple validity times in a group.

app/Domains/Event/Services/EventService.php

@@ -15,7 +15,7 @@ class EventService
 
     public function forTenant(Tenant $tenant): Tenant
     {
-        return $tenant->load(['eventDates', 'socialMedia']);
+        return $tenant->load(['eventDates.validityTime', 'socialMedia']);
     }
 
     /** @param array<string, mixed> $data */
@@ -35,7 +35,7 @@ class EventService
                 $this->syncLegacyContact($tenant, $data['contact']);
             }
 
-            return $tenant->load(['eventDates', 'socialMedia']);
+            return $tenant->load(['eventDates.validityTime', 'socialMedia']);
         });
     }