feat: add rate limiting and more error handling to Cal.ai

[DexterStorey]

What does this PR do?

This PR adds:

• Rate Limiting (20 emails / day / user)

• A catch all error for OpenAI rate limit and any other funky action in agent loop that tells user to try again later

Fixes #11916

Requirement/Documentation

Type of change

• New feature (non-breaking change which adds functionality)

How should this be tested?

To test rate limit: send more than 20 emails / day
To test agent loop 500 catch: overspend OpenAI tokens or use a bad OpenAI API key

• Tested rate limiting by sending too many requests
• Confirmed everything else still works with standard tests "Create a booking with...", "What meetings do I have...", etc.

Mandatory Tasks

• Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

Checklist

• I haven't read the contributing guide
• My code doesn't follow the style guidelines of this project
• I haven't commented my code, particularly in hard-to-understand areas
• I haven't checked if my PR needs changes to the documentation
• I haven't checked if my changes generate no new warnings
• I haven't added tests that prove my fix is effective or that my feature works
• I haven't checked if new and existing unit tests pass locally with my changes

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 17, 2023 5:28pm

[vercel]

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

A member of the Team first needs to authorize it.

[github-actions]

Thank you for following the naming conventions! 🙏 Feel free to join our discord and post your PR link to collect XP and win prizes!

[DexterStorey]

!!!IMPORTANT!!!

We needed to swap this TRPC import from client side to server side because the AI app uses it server side.
Rate limiting in our use case Does not work without this.

We need a senior engineer on Cal team to verify that this change is okay.

We don't know if this has upstream repercussions or if it's no prob.

Please don't merge this without checking this out. 🙏

[DexterStorey]

@zomars @emrysal @PeerRich

Flagging this, otherwise, this PR should be good to 🚀

[sean-brydon]

This looks safe to me <3

This is only ever ran on the server in all of use cases.

[keithwillcode]

Yeah this looks like an ideal change actually

[github-actions]

📦 Next.js Bundle Analysis for @calcom/web

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

This PR introduced no changes to the JavaScript bundle! 🙌

[sean-brydon]

LGTM - always called on server side so that change is fine

NIT: we should move this to a HTTP error in future as now its not always called within trpc

[DexterStorey]

Fixes: #11916