Refactor ticket validity handling and improve tests

- Updated tests for Accommodation, Entry, Food, Merchandise, and Sale controllers to use soft deletes for variants and ensure proper inventory counts.
- Enhanced ticket generation logic to resolve validity from soft-deleted catalog sources.
- Introduced a new TicketValidityResolver service to manage ticket validity based on event dates and variant definitions.
- Removed unnecessary database assertions and improved the clarity of validity checks in tests.
- Added comprehensive tests for the new TicketValidityResolver service, ensuring correct handling of event dates and multi-select options.
- Cleaned up unused code and assertions in existing tests for better maintainability.

app/Domains/Ticket/Exceptions/TicketGenerationException.php

@@ -3,6 +3,7 @@
 namespace App\Domains\Ticket\Exceptions;
 
 use App\Domains\Catalog\Models\CatalogItem;
+use App\Domains\Catalog\Models\Variant;
 use App\Domains\Purchase\Models\Purchase;
 use App\Domains\Purchase\Models\PurchaseItem;
 use RuntimeException;
@@ -24,9 +25,9 @@ class TicketGenerationException extends RuntimeException
         return new self(__('api.ticket.disabled', ['product' => $catalogItem->id]));
     }
 
-    public static function ambiguousValidityTime(CatalogItem $catalogItem): self
+    public static function invalidValidityConfiguration(CatalogItem $catalogItem, Variant $variant): self
     {
-        return new self("Catalog item {$catalogItem->id} resolves more than one validity time.");
+        return new self("Variant {$variant->id} from catalog item {$catalogItem->id} has an invalid validity configuration.");
     }
 
     public static function variantNotFound(