feat: option to enforce language for bookingPage

[vijayraghav-io]

What does this PR do?

• Fixes [CAL-5043] event-type: option to enforce a language for the booking page (default: visitors browser language) #18710
• Fixes CAL-5043

/claim #18710

https://www.loom.com/share/50790635a82f4767a4c1824167daf096?sid=acfe7870-5c4e-4c21-9997-724da66b7fde

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• - N/A- 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.

[vercel]

@vijayraghav-io is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[graphite-app]

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (01/21/25)

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

"Add community label" took an action on this PR • (01/21/25)

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

[Praashh]

why catch {} ??

[vijayraghav-io]

as a fallback, if useLocale is called from non-booker components , it should use global locale or the atom context locale (as per prev or existing flow).

instead of having this entire snippet inside catch

if (context?.clientId) {
    return {
      i18n: context.i18n,
      t: context.t,
      isLocaleReady: true,
    } as unknown as {
      i18n: ReturnType<typeof useTranslation>["i18n"];
      t: ReturnType<typeof useTranslation>["t"];
      isLocaleReady: boolean;
    };
  }
  return {
    i18n,
    t,
    isLocaleReady,
  };

leaving catch {} looked legit to me, also its not required to log here for non-booker components as it's normal flow.
try {} is used here as useBookerI18n() throws error for non-booker components

[github-actions]

E2E results are ready!

• Workflow #44842.1 latest results