fix: view team bookings

[SomayChauhan]

What does this PR do?

re-doing #13591 - that was reverted due to DB load issues introduced.

Fixes #13582

[graphite-app]

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (03/14/24)

1 reviewer was added to this PR based on Keith Williams's automation.

"Add community label" took an action on this PR • (03/14/24)

1 label was added to this PR based on Keith Williams's automation.

"Add foundation team as reviewer" took an action on this PR • (03/14/24)

1 reviewer was added to this PR based on Keith Williams's automation.

[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! 🙌

[joeauyeung]

From this comment, I'm not seeing any select fields in the queries. #13591 (review)

Let's figure out the minimum amount of data we need from the DB for this endpoint.

[SomayChauhan]

@joeauyeung how about now?

[joeauyeung]

@SomayChauhan I like this commit: 0aa47bd (#14079)

I'll approve for now, but let's see what @keithwillcode and @zomars have to say.

As a follow up I found two things that we can improve on:

• getUniqueBookings filters duplicate bookings based on uid but when getting the nested fields from the bookings we filter on id. We should change getUniqueBookings to filter on just ids to reduce the amount of data we need to initially query the database for.
• Optimize getUniqueBookings
  • Right now it loops through the array of bookings theoretically two times but I think we can cut it down to once

const getUniqueBookings = <T extends { uid: string }>(arr: T[]) => {
	const  unique = new Set();
    arr.forEach((booking) => {
    set.add(booking.uid);
  	});
  return [ ...unique.values() ];
};

[zomars]

For some reason e2e tests are broken. Will revisit after release.

[emrysal]

Tests passing, looks ready to go! :)