fix: react incompatiblity with nextjs error

[retrogtx]

What does this PR do?

Updated the peer dependencies in @calcom/embed-react to support both Rect 18 and 19. This change allows the embed component to work with Nextjs projects which use React 19.

since the codebase is huge,

• the change updates peer dependencies to accept both React 18 and React 19 versions
• it also maintains backward compatibility with existing React 18 applications

• Fixes Peer dependencies pinned to React 18.2 incompatible with latest nextjs #18399 (GitHub issue number)

No errors regarding react compatibility anymore.

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.

[vercel]

@retrogtx 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/01/25)

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

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

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

"Add ready-for-e2e label" took an action on this PR • (01/01/25)

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

[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 #18399: react incompatiblity with nextjs error". 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

[hariombalhara]

LGTM !! Thanks @retrogtx 🙏

[retrogtx]

LGTM !! Thanks @retrogtx 🙏

thank you and happy new years!

[github-actions]

E2E results are ready!

• Workflow #42707.1 latest results