feat(traceability): add lot genealogy and recall workflows

[puemos]

Problem

Food producers need a durable traceability chain from supplier ingredient lots, through production batches, to the customer orders that received finished goods. Craftplan did not preserve enough receipt and consumption provenance to support forward traces, backward traces, or an operational recall workflow.

Fix

• Capture supplier lot codes, expiry dates, split lots, and partial deliveries while receiving purchase orders.
• Freeze ingredient-lot consumption and product details on completed batches so historical genealogy and labels remain stable when catalog data changes.
• Add a responsive Trace Center with forward, backward, and recall modes, lot hold/release controls, CSV export, print output, and customer destinations.
• Add A5 and compact finished-batch labels with barcodes, setup warnings, and responsive documentation screenshots.

Tests

• mix test — 430 passed, 1 skipped, 5 excluded.
• cd docs && pnpm run build — 15 documentation pages built successfully.
• Chrome DevTools Protocol E2E checks for forward/backward tracing, recall hold/release, split and partial receiving, batch-label variants, and desktop/mobile overflow.

Notes

• Adds database migrations and matching Ash resource snapshots for traceability, receiving, production allocation, and label metadata.
• Deployments must run the new migrations before serving this version.
• Closes Feature request: EU requirement - traceability #39.