feat: apple calendar connect atom

[Ryukemeister]

What does this PR do?

• Adds connect to apple calendar atom for apple calendar integration

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected)
• I have added a Docs issue here if this PR makes changes that would require a documentation change
• I have added or modified automated tests that prove my fix is effective or that my feature works (PRs might be rejected if logical changes are not properly tested)

How should this be tested?

This can be tested in the examples app under packages/platform/examples/base. The steps to run examples app are as follows:

1. Go to packages/platform/atoms and run yarn dev
2. Go to apps/api/v2 and run yarn dev
3. Go to packages/platform/examples/base and run yarn prisma db push and after that run yarn dev

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

✅ Ryukemeister
✅ ThyMinimalDev
❌ Rajiv Sahal

---

Rajiv Sahal seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
ai	⬜️ Ignored (Inspect)	Visit Preview		Jun 27, 2024 3:29pm
cal	⬜️ Ignored (Inspect)	Visit Preview		Jun 27, 2024 3:29pm
calcom-web-canary	⬜️ Ignored (Inspect)	Visit Preview		Jun 27, 2024 3:29pm

[github-actions]

📦 Next.js Bundle Analysis for @calcom/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Twenty-one Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/[user]/[type]	416.68 KB	644.38 KB	184.11% (🟡 +0.15%)
/[user]/[type]/embed	416.68 KB	644.38 KB	184.11% (🟡 +0.15%)
/apps/[slug]/[...pages]	593.37 KB	821.07 KB	234.59% (🟡 +0.21%)
/auth/saml-idp	12.22 KB	239.92 KB	68.55% (🟢 -20.80%)
/d/[link]/[slug]	416.48 KB	644.18 KB	184.05% (🟡 +0.15%)
/event-types	566.4 KB	794.09 KB	226.88% (🟡 +0.30%)
/event-types/[type]	442.05 KB	669.75 KB	191.36% (🟡 +0.15%)
/org/[orgSlug]/[user]/[type]	416.88 KB	644.58 KB	184.16% (🟡 +0.15%)
/org/[orgSlug]/[user]/[type]/embed	416.9 KB	644.6 KB	184.17% (🟡 +0.15%)
/org/[orgSlug]/instant-meeting/team/[slug]/[type]	416.5 KB	644.2 KB	184.06% (🟡 +0.14%)
/org/[orgSlug]/team/[slug]/[type]	416.69 KB	644.39 KB	184.11% (🟡 +0.15%)
/settings/admin/lockedSMS/UsersTable	79.91 KB	307.61 KB	87.89% (🟢 -0.16%)
/settings/admin/lockedSMS/lockedSMSView	119.39 KB	347.09 KB	99.17% (🟢 -0.19%)
/settings/admin/oAuth/oAuthView	95.44 KB	323.14 KB	92.33% (🟢 -0.19%)
/settings/organizations/[id]/about	159.6 KB	387.3 KB	110.66% (🟡 +0.45%)
/settings/organizations/[id]/add-teams	159.59 KB	387.29 KB	110.65% (🟡 +0.46%)
/settings/organizations/new	159.6 KB	387.3 KB	110.66% (🟡 +0.45%)
/settings/platform/new	120.65 KB	348.34 KB	99.53% (🟡 +0.50%)
/team/[slug]/[type]	416.66 KB	644.36 KB	184.10% (🟡 +0.15%)
/team/[slug]/[type]/embed	416.69 KB	644.39 KB	184.11% (🟡 +0.15%)
/video/[uid]	290.75 KB	518.44 KB	148.13% (🟢 -0.31%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.