fix(bookings): apply attendeeEmail filter correctly

[ankitsingh1421]

What does this PR do?

• Fixes get all bookings filter #28512

This PR fixes an issue where the attendeeEmail query parameter in GET /v2/bookings was not applied correctly.

Problem

The API was returning all bookings regardless of the provided attendeeEmail filter.

Solution

• Implemented proper filtering logic for attendeeEmail
• Ensured exact match filtering on attendee email
• Aligned filtering behavior with expected API functionality

---

Visual Demo (For contributors especially)

Image Demo (if applicable):

Before Fix:

• API returns all bookings (ignores attendeeEmail)

After Fix:

• API returns only bookings matching the provided attendeeEmail

(Unable to attach screenshots due to local environment issues, but logic has been verified.)

---

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox. (N/A)
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

---

How should this be tested?

Setup

• Ensure environment variables like CALCOM_API_KEY are set
• Run project locally using Docker or yarn dx

Test Steps

1. Create 3 bookings with different attendee emails:

   • attendee-a@example.com
   • attendee-b@example.com
   • attendee-c@example.com

2. Call the API:

GET /v2/bookings?take=100&eventTypeId={eventTypeId}&attendeeEmail=attendee-a%40example.com

Expected Result (Happy Path)

• totalCount should be 1
• Only booking with attendee-a@example.com should be returned

Previous Behavior

• All bookings were returned (filter ignored)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Singh 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.}

[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/attendee email filter". 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 3 files

[Ryukemeister]

Review: were

[Ryukemeister]

dont think we need these changes can you please revert these

[ankitsingh1421]

Thanks for the suggestions!

I've:

• Reverted the unrelated env changes
• Removed the duplicate attendeeEmail field and used the existing one in filters
• Ensured filtering logic works as expected

Would appreciate another review 🙏