ed0c9392a9
* fix: split confirm-emails e2e test to authenticate as booking owner The test was flaky because it authenticated as an admin user (authEmail) but created bookings for different users (emailsEnabledSetup.user and emailsDisabledSetup.user). When confirming/declining bookings, the ApiAuthGuard + BookingUidGuard rejected requests with 401 because the authenticated user wasn't the booking owner. The fix splits the test into two separate describe blocks, each with its own app instance that authenticates as the actual booking owner. This ensures the authenticated user always matches the booking owner. Co-Authored-By: anik@cal.com <adhabal2002@gmail.com> * fix: add unauthenticated app for attendee reschedule test Co-Authored-By: anik@cal.com <adhabal2002@gmail.com> * fix: use real API key authentication instead of withApiAuth mock - Replace withApiAuth mock with real API key authentication using ApiKeysRepositoryFixture - This avoids Passport strategy registration conflicts between test suites - For attendee reschedule test, use unauthenticated request (no auth header) since endpoint uses OptionalApiAuthGuard - Remove separate unauthenticatedApp instance as it's no longer needed Co-Authored-By: anik@cal.com <adhabal2002@gmail.com> * fix flakes * update --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>