chore: [Booking Cancellation Refactor - 2] Inject repositories and use them instead of Prisma in cancellation flow

[tomerqodo]

Benchmark PR from qodo-benchmark#664

---

Note

Modernizes the booking cancellation flow to use repository-based DI instead of direct Prisma and adds supporting infrastructure and tests.

• Switches handleCancelBooking and API BookingCancelService to injected user, booking, profile, bookingReference, and attendee repositories
• Adds methods to BookingRepository (updateMany, updateIncludeWorkflowRemindersAndReferences, findManyIncludeWorkflowRemindersAndReferences) and implements DTO interfaces (IBookingRepository, IBookingReferenceRepository, IProfileRepository)
• Implements PrismaBookingAttendeeRepository with deleteManyByBookingId and extends BookingReferenceRepository with updateManyByBookingId
• Wires new DI modules/tokens for BookingReferenceRepository, BookingAttendeeRepository, and ProfileRepository; updates Nest module providers in booking-cancel.module.ts
• Updates ProfileRepository to be DI-ready and adds findFirstByUserId
• Adds tests covering seated event attendee deletion, bulk/subsequent recurring cancellations, and booking reference cleanup

^{Written by Cursor Bugbot for commit 72b8c3a. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Missing locale field causes incorrect organizer translation

Medium Severity

The locale field was removed from userSelect in UserRepository.ts, but handleCancelBooking.ts still accesses organizer.locale at lines 337 and 370 to determine the organizer's translation language. Since findByIdOrThrow uses userSelect which no longer includes locale, the organizer's locale will always be undefined, causing the translation to fall back to "en" regardless of the organizer's actual language preference. This affects cancellation emails and notifications.

Additional Locations (1)

• packages/features/bookings/lib/handleCancelBooking.ts#L336-L337

 

[cursor]

Query filter mismatch in recurring booking cancellation

Medium Severity

The findManyIncludeWorkflowRemindersAndReferences query uses gte: bookingToDelete.startTime while the preceding updateMany uses a conditionally computed gte value (cancelSubsequentBookings ? bookingToDelete.startTime : new Date()). When allRemainingBookings is true but cancelSubsequentBookings is false, the updateMany cancels bookings from new Date() onwards, but the find query fetches bookings from bookingToDelete.startTime, potentially including bookings that weren't actually cancelled.

Additional Locations (1)

• packages/features/bookings/lib/handleCancelBooking.ts#L497-L512