feat(ticket): implement validity time management for tickets and catalog items

- Added ValidityTime model and migration to manage ticket validity periods.
- Updated TicketGeneratorService to resolve and assign validity times to tickets.
- Refactored ticket generation logic to remove legacy date fields and use validity time.
- Introduced timezone support for tenants to handle service dates correctly.
- Updated migrations to remove deprecated columns and add foreign keys for validity times.
- Modified seeders and tests to accommodate new validity time structure.
- Enhanced tests to validate ticket generation and validity time behavior.

tests/Feature/Catalog/CatalogSchemaTest.php

@@ -44,8 +44,7 @@ class CatalogSchemaTest extends TestCase
             'precio',
             'inventory_policy',
             'has_tickets',
-            'maximum_use_date',
-            'minimum_use_date',
+            'validity_time_id',
         ], Schema::getColumnListing('catalog_items'));
     }
 
@@ -183,8 +182,6 @@ class CatalogSchemaTest extends TestCase
     {
         $this->assertTrue(Schema::hasColumns('variantes', [
             'event_date_id',
-            'minimum_use_date',
-            'maximum_use_date',
         ]));
     }