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

[tomerqodo]

Benchmark PR from qodo-benchmark#682

---

Note

Modernizes the booking cancellation flow by replacing direct Prisma calls with injected repositories and expanding DI wiring across API and features packages.

• Replace direct DB access in handleCancelBooking with injected userRepository, bookingRepository, profileRepository, bookingReferenceRepository, and attendeeRepository; handler now accepts dependencies and service wires them via DI
• Introduce/implement repo interfaces: IBookingRepository, IBookingReferenceRepository, IProfileRepository, IBookingAttendeeRepository; extend BookingRepository with updateMany, updateIncludeWorkflowRemindersAndReferences, and findManyIncludeWorkflowRemindersAndReferences; add BookingReferenceRepository.updateManyByBookingId; make ProfileRepository DI-aware with findFirstByUserId
• Add DI modules/tokens for attendee/reference/profile repos and update BookingCancelService.module and API BookingCancelModule providers; export new repos via @calcom/platform-libraries/repositories
• Tests: add cases for seated event attendee cleanup, recurring all-remaining/subsequent cancellations, and booking reference cleanup during cancellation

^{Written by Cursor Bugbot for commit 8cb1511. 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]

Query uses wrong date filter for recurring bookings

High Severity

When cancelling recurring bookings with allRemainingBookings=true, the updateMany call uses gte: new Date() (via the gte variable) to cancel bookings from now onwards, but findManyIncludeWorkflowRemindersAndReferences uses gte: bookingToDelete.startTime which could be in the past. This mismatch causes the find query to return bookings that weren't actually cancelled, potentially deleting workflow reminders for active bookings. The find query should use the same gte variable to ensure consistency with what was actually cancelled.

 

[cursor]

Missing locale field breaks organizer language preference

Medium Severity

The locale field was removed from userSelect in UserRepository.ts, but handleCancelBooking.ts still accesses organizer.locale to determine the translation language. Since locale is no longer selected, organizer.locale is always undefined, causing all organizer communications (emails, translations) to default to English regardless of the organizer's actual language preference.

Additional Locations (1)

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