Refactor Catalog API: Remove Create Catalog Item Endpoint and Update Related Logic

- Removed the "Create Catalog" endpoint from the Postman collection.
- Updated the CatalogController to handle tenant-specific catalog items based on active events.
- Refactored CatalogItem model to automatically set event_id based on tenant's active_event_id during creation.
- Deleted StoreCatalogItemRequest and CatalogItemResource as they are no longer needed.
- Updated various services and controllers to utilize the new tenant-based catalog item retrieval logic.
- Added tests to ensure that catalog reads are limited to items associated with the active event.

app/Domains/Ticketing/FiestaFutbolInfantil/Services/FoodService.php

@@ -33,7 +33,7 @@ class FoodService
     public function current(Tenant $tenant): ?CatalogItem
     {
         return CatalogItem::query()
-            ->where('tenant_code', $tenant->codigo)
+            ->forTenantCatalog($tenant)
             ->where('slug', 'comida')
             ->with([
                 'variants.catalogItem',
@@ -119,7 +119,7 @@ class FoodService
     {
         return DB::transaction(function () use ($tenant, $variants): CatalogItem {
             $food = CatalogItem::query()
-                ->where('tenant_code', $tenant->codigo)
+                ->forTenantCatalog($tenant)
                 ->where('slug', 'comida')
                 ->lockForUpdate()
                 ->firstOrFail();
@@ -233,7 +233,7 @@ class FoodService
             'nombre' => 'Comidas',
         ]);
         $food = CatalogItem::withTrashed()
-            ->where('tenant_code', $tenant->codigo)
+            ->forTenantCatalog($tenant)
             ->where('slug', 'comida')
             ->lockForUpdate()
             ->first();