fix: Tooltip must be used within TooltipProvider

[muhammadspace]

Fix #16833

After installing Cal.com for the first time, users are not able to run go through the setup process on the client due to PageWrapper not being applied to /auth/setup.

• Fixes Tooltip must be used within TooltipProvider #16833

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 added a Docs issue here 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?

1. Do a fresh install of Cal.com; clone the repo into a new workspace and run yarn dev after installing dependencies
2. Create a new Postgres DB so that Cal.com recognizes that a setup is required
3. Head over to localhost:3000.
4. After getting redirected to localhost:3000/auth/setup, an error will occur: "Tooltip must be used within TooltipProvider"

• Are there environment variables that should be set?
  Nope
• What are the minimal test data to have?
  An new DB with no users
• What is expected (happy path) to have (input and output)?
  No errors when going to localhost:3000/auth/setup
• Any other important info that could help to test that PR

[vercel]

@muhammadspace is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize 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 "fixes #16833". 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

[graphite-app]

Graphite Automations

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

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

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

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

"Add ready-for-e2e label" took an action on this PR • (10/03/24)

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

[anikdhabal]

Great find @muhammadspace

[github-actions]

E2E results are ready!

• Workflow #33566.1 latest results

[FrancoAlbarra]

i still get this error deploying on render

[FrancoAlbarra]

i still get this error deploying on render

Also getting this error on console and the hole page goes blank first i get a error waring 505 but after a few seconds dissapears

Thanks you for reading i hope we can fix this soon,
regards

[anikdhabal]

i still get this error deploying on render

Thanks for reporting; will check that. Also, these changes have not been shipped to production yet

[FrancoAlbarra]

i still get this error deploying on render

Thanks for reporting; will check that. Also, these changes have not been shipped to production yet

ok, i'll wait for the solution to be publish

[FrancoAlbarra]

any news on this?

[anikdhabal]

any news on this?

Yeah, it's was shipped. Could you pls check