feat(intake): structured per-service intake questions

Services declare up to 8 intake fields (text/yesno, required) stored
as JSONB; shared/intake.go is the single normalization point — slug
keys, label/dup/unknown-key rules, yes/no canonicalization. Booking
create validates answers against the service declaration (missing
required -> 400), unknown keys are dropped before persist.

Answers surface on UpcomingBooking and CustomerBookingView; the
services page gains a compact editor and the public form renders
declared questions under contact details. Verified live end-to-end.

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

apps/backend/internal/bookings/customer_service.go

@@ -11,6 +11,7 @@ import (
 	"bookra/apps/backend/internal/db"
 	"bookra/apps/backend/internal/domain"
 	"bookra/apps/backend/internal/notifications"
+	"bookra/apps/backend/internal/shared"
 )
 
 var (
@@ -134,6 +135,7 @@ func (s *CustomerService) GetBookingByReference(ctx context.Context, reference s
 		Location:         locationName,
 		Status:           booking.Status,
 		Notes:            booking.Notes,
+		Intake:           shared.ParseIntakeAnswers(booking.Intake),
 		WaitlistPosition: position,
 	}, nil
 }