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/Event/Services/EventService.php

@@ -4,6 +4,7 @@ namespace App\Domains\Event\Services;
 
 use App\Domains\Tenant\Models\Tenant;
 use Illuminate\Support\Facades\DB;
+use Illuminate\Validation\ValidationException;
 
 class EventService
 {
@@ -60,7 +61,19 @@ class EventService
             }
         }
 
-        $existingDates->slice(count($dates))->each->delete();
+        $datesToDelete = $existingDates->slice(count($dates));
+
+        if ($datesToDelete->contains(fn ($eventDate): bool => $eventDate
+            ->selectedByVariants()
+            ->whereHas('sourceTickets')
+            ->exists()
+            || $eventDate->variants()->whereHas('sourceTickets')->exists())) {
+            throw ValidationException::withMessages([
+                'dates' => ['No se puede eliminar una fecha utilizada por tickets generados.'],
+            ]);
+        }
+
+        $datesToDelete->each->delete();
         $tenant->unsetRelation('eventDates');
     }