What does this PR do?

• Fixes #XXXX (GitHub issue number)
• Fixes CAL-XXXX (Linear issue number - should be visible at the bottom of the GitHub issue description)

Visual Demo (For contributors especially)

A visual demonstration is strongly recommended, for both the original and new change (video / image - any one).

Video Demo (if applicable):

• Show screen recordings of the issue or feature.
• Demonstrate how to reproduce the issue, the behavior before and after the change.

Image Demo (if applicable):

• Add side-by-side screenshots of the original and updated change.
• Highlight any significant change(s).

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.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

• Are there environment variables that should be set?
• What are the minimal test data to have?
• What is expected (happy path) to have (input and output)?
• Any other important info that could help to test that PR

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 changes generate no new warnings

Summary by cubic

Put the bookings redesign behind a new team-scoped feature flag so we can roll it out safely. Legacy bookings list remains the default; the new list + calendar experience is shown only when the flag is enabled.

• New Features

  • Added a new feature flag: bookings-v3 (team/org scoped), with Prisma migration and flags config/hooks updates.
  • Bookings page now gates the redesigned list and calendar views behind bookings-v3; falls back to the legacy list when disabled.
  • Added a view toggle (?view=list|calendar) and force list view on mobile.
  • Introduced a BookingDetailsSheet store (Zustand) with selectedId in the URL for deep linking and next/previous navigation.
  • Added JoinMeetingButton and a joinable location helper to surface meeting links; refined skeletons, media query handling, and DataTable row attributes; updated tests and selectors.

• Migration

  • Run the Prisma migration to insert the bookings-v3 feature.
  • Enable per org/team by setting bookings-v3 to true (checked via FeaturesRepository.checkIfTeamHasFeature).
  • No breaking changes; legacy list remains the default until the flag is enabled.

^{Written for commit bf7b8d6. Summary will update automatically on new commits.}