fix(api-v2): correctly parse ISO timezone offsets when rescheduling bookings (calcom#28333)

* fix(api-v2): correctly parse ISO timezone offsets when rescheduling bookings

closes: calcom#28310

* fix: clarify reschedule endpoint requires UTC timezone

Signed-off-by: Hemant M Mehta <hemant29mehta@gmail.com>

---------

Signed-off-by: Hemant M Mehta <hemant29mehta@gmail.com>
Co-authored-by: Rajiv Sahal <sahalrajiv-extc@atharvacoe.ac.in>
Co-authored-by: Peer Richelsen <peeroke@gmail.com>
Co-authored-by: Sahitya Chandra <sahityajb@gmail.com>
Co-authored-by: Romit <85230081+romitg2@users.noreply.github.com>

Author: 5 people

packages/platform/types/bookings/2024-08-13/inputs/reschedule-booking.input.ts

@@ -8,8 +8,8 @@ owner will have to confirm the rescheduled booking.`;
 export class RescheduleBookingInput_2024_08_13 {
   @IsDateString()
   @ApiProperty({
-    description: "Start time in ISO 8601 format for the new booking",
-    example: "2024-08-13T10:00:00Z",
+    description: "The start time of the booking in ISO 8601 format in UTC timezone.",
+    example: "2024-08-13T09:00:00Z",
   })
   start!: string;
 
@@ -47,8 +47,8 @@ export class RescheduleBookingInput_2024_08_13 {
 export class RescheduleSeatedBookingInput_2024_08_13 {
   @IsDateString()
   @ApiProperty({
-    description: "Start time in ISO 8601 format for the new booking",
-    example: "2024-08-13T10:00:00Z",
+    description: "The start time of the booking in ISO 8601 format in UTC timezone.",
+    example: "2024-08-13T09:00:00Z",
   })
   start!: string;