Update LOT API to use nested batch_origin_entries structure

Each spice now returns an `origins` array (was single `origin` object) with
supplier and farmer resolved from the new entries relation, not flat columns.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

app/Http/Controllers/Api/LotController.php

@@ -16,7 +16,8 @@ class LotController extends Controller
             'size.packing',
             'recipe.spices',
             'origins.spice',
-            'origins.supplier',
+            'origins.entries.supplier',
+            'origins.entries.farmer',
         ])->where('lot_number', $lotNumber)->first();
 
         if (! $batch) {

app/Http/Resources/LotResource.php

@@ -35,12 +35,14 @@ class LotResource extends JsonResource
                 return [
                     'name'       => $spice->name,
                     'percentage' => (float) $spice->pivot->amount_in_percent,
-                    'origin'     => $origin ? [
+                    'origins'    => $origin
-                        'country'  => $origin->origin_country,
+                        ? $origin->entries->map(fn ($e) => [
-                        'farmer'   => $origin->farmer,
+                            'country'  => $e->origin_country,
-                        'supplier' => $origin->supplier?->name,
+                            'supplier' => $e->supplier?->name,
-                        'notes'    => $origin->notes,
+                            'farmer'   => $e->farmer?->name,
-                    ] : null,
+                            'notes'    => $e->notes,
+                        ])->values()
+                        : [],
                 ];
             })->values(),
         ];