fix: calendar events not syncing with v2 api bookings

[a-tokyo]

Closes #25009

Issue Summary

API v2 POST /bookings creates ACCEPTED bookings but fails to sync to calendar or send emails - Regression of #16512

When creating bookings via the Cal.com API v2 (POST /v2/bookings), bookings were created successfully with status: "ACCEPTED" and appeared on the dashboard, but did not sync to the connected calendar (Google/Outlook) and no confirmation emails were sent.
The API response contained an empty references: [] array, indicating that no calendar event was created.

---

What does this PR do?

• Fixes API v2 POST /bookings creates ACCEPTED bookings but fails to sync to calendar or send emails - Regression of #16512 #25009
• Fixes CAL-XXXX (Linear issue reference)

Summary of changes:

• Added the missing areCalendarEventsEnabled: true flag when creating new requests from the API.
• This ensures both calendar sync and email notifications are triggered properly for bookings created via API v2.

Files changed:

• apps/api/v2/src/ee/bookings/2024-08-13/services/input.service.ts
  • 1 addition, 1 deletion

- Object.assign(newRequest, { userId });
+ Object.assign(newRequest, { userId, areCalendarEventsEnabled: true });

---

Visual Demo

Before:

• Booking created via API appears in dashboard but not on connected calendar.
• No confirmation email sent.

After:

• Booking appears in both dashboard and connected calendar.
• Confirmation email is sent to attendee and host.

---

Mandatory Tasks

• I have self-reviewed the code.
• N/A (no documentation changes needed).
• Verified fix manually via API and connected Google Calendar.

---

How should this be tested?

1. Connect a Google Calendar integration.
2. Send a POST /v2/bookings request with a valid booking payload.
3. Verify:
   • Booking status: ACCEPTED
   • Calendar event is created in Google Calendar
   • Confirmation emails are sent to both host and attendee
   • API response contains non-empty references

Expected:
Calendar sync and email notifications now function correctly for API v2 bookings.

---

[vercel]

@a-tokyo is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title " fix: calendar events not syncing with v2 api bookings". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[cubic-dev-ai]

No issues found across 1 file

[dhairyashiil]

Please attach before and after loom video, making it draft until then.

[anikdhabal]

Going with this one:- #25049 🙏