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

[tomerqodo]

Benchmark PR from agentic-review-benchmarks#3

[sentry]

Bug: When cancelling subsequent recurring bookings, the findMany query for reminder cleanup uses a different gte time filter than the updateMany query that performs the cancellation.
_{Severity: MEDIUM}

Suggested Fix

The findMany operation should use the same gte variable that was calculated for and used by the updateMany operation. This ensures that reminder cleanup is performed on the exact same set of bookings that were cancelled.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: packages/features/bookings/lib/handleCancelBooking.ts#L513-L518

Potential issue: When cancelling subsequent recurring bookings where
`cancelSubsequentBookings` is true, the logic to cancel bookings and the logic to clean
up their reminders use different time filters. The cancellation query (`updateMany`)
uses `startTime: { gte: new Date() }`, while the subsequent query to find bookings for
reminder deletion (`findMany`) uses `startTime: { gte: bookingToDelete.startTime }`.
This mismatch can cause workflow reminders to be deleted for bookings that were not
actually cancelled, specifically when cancelling a booking that has already started but
not yet ended.

_{Did we get this right? 👍 / 👎 to inform future reviews.}