[CAL-4431] RescheduledBy feature needs more fixes

[alishaz-polymath]

After a successfully rescheduling a booking using the rescheduledBy url parameter. ie- /reschedule/{{uuid}}[email protected]   The user is then redirected to the booking/{{uuid}} url for the booking success/confirmation page.

• But this redirect on the reschedule success flow doesn’t carry across the rescheduledBy that was used during the first reschedule.

• This means if the user decides to reschedule again immediately after the first reschedule, then this rescheduledBy data is lost.

• could this flow be changed to include the rescheduledBy or cancelledBy in the url when redirected

• Also on this booking/{{uuid}} page, the URL on the Reschedule button at the bottom also only checks the cancelledBy url param. As it currently will ignore this value. So including it the success redirect wouldn't work unless this is also changed.

_{From SyncLinear.com | CAL-4431}

[naaa760]

Hello!! @alishaz-polymath

**Include rescheduledBy Parameter in Redirect**: Append the rescheduledBy parameter to the redirect URL for the booking confirmation page to retain essential information.

**Update Reschedule Button Logic:** Modify the Reschedule button to check for both rescheduledBy and cancelledBy parameters, allowing seamless future rescheduling for users.