fix(bookings): auto-confirm rescheduled paid bookings when confirmation is not required

[jaydeep-pipaliya]

What does this PR do?

Fixes #22857

When an attendee reschedules a paid booking on an event type that does not require confirmation, the rescheduled booking was incorrectly created with PENDING status instead of ACCEPTED. This caused:

• Duplicate "unconfirmed" bookings piling up
• Hosts having to manually confirm rescheduled sessions that were already paid
• Broken CRM integrations receiving duplicate booking records

Root cause

In getRequiresConfirmationFlags.ts, the determineIsConfirmedByDefault function:

return (!requiresConfirmation && price === 0) || userReschedulingIsOwner;

When requiresConfirmation = false and price > 0 (paid event), this returns false — even when rescheduling an already-paid booking. The price check blocks auto-confirmation because it assumes payment hasn't been collected yet.

Fix

Added originalRescheduledBookingPaid parameter to determineIsConfirmedByDefault. When the original booking was already paid and the event type doesn't require confirmation, the rescheduled booking is auto-confirmed:

if (originalRescheduledBookingPaid && !requiresConfirmation) {
  return true;
}

Changes

• packages/features/bookings/lib/handleNewBooking/getRequiresConfirmationFlags.ts — accept and use originalRescheduledBookingPaid flag
• packages/features/bookings/lib/service/RegularBookingService.ts — pass originalRescheduledBooking.paid to the flags function