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.

app/Domains/Ticket/Exceptions/TicketGenerationException.php

@@ -24,9 +24,9 @@ class TicketGenerationException extends RuntimeException
         return new self(__('api.ticket.disabled', ['product' => $catalogItem->id]));
     }
 
-    public static function maximumUseDateReached(CatalogItem $catalogItem): self
+    public static function ambiguousValidityTime(CatalogItem $catalogItem): self
     {
-        return new self(__('api.ticket.expired', ['product' => $catalogItem->id]));
+        return new self("Catalog item {$catalogItem->id} resolves more than one validity time.");
     }
 
     public static function variantNotFound(