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.

tests/Feature/Forms/AdminAppFoodFormControllerTest.php

@@ -38,7 +38,7 @@ class AdminAppFoodFormControllerTest extends TestCase
             'dominio' => 'fiesta.test',
             'website_type_code' => 'onticket',
         ]);
-        $tenant->eventDates()->create([
+        $eventDate = $tenant->eventDates()->create([
             'date' => '2026-10-09',
             'time_start' => '00:00',
             'time_end' => '23:59',
@@ -60,6 +60,8 @@ class AdminAppFoodFormControllerTest extends TestCase
             ->assertOk()
             ->assertJsonCount(1, 'data.event_dates')
             ->assertJsonPath('data.event_dates.0.date', '2026-10-09')
+            ->assertJsonPath('data.event_dates.0.validity_time_id', $eventDate->validity_time_id)
+            ->assertJsonPath('data.event_dates.0.validity_time.type', 'fixed_window')
             ->assertJsonPath('data.schedules.0.value', 'Almuerzo')
             ->assertJsonPath('data.schedules.1.value', 'Cena')
             ->assertJsonPath('data.services.0.value', 'Comedor');