Batch Clone Events to a different Booking

Batch event cloning now supports cloning Events to a different Booking.

: All cloned Events will now default to the Lead status, regardless of the original Event's status (e.g., Definite). This update separates conflict checking from the cloning process. Cloning Events as Lead status ensures there are no conflicts during the initial cloning. It's possible to later edit the status, and any conflicts will be displayed and can be addressed.