feat: removed the confirm step in creating bookings

[theVedanta]

What does this PR do?

Removed the confirm step changes in this PR because as I see it, once the URL params are passed and checked in the useEffect, the booking state is changed, where I've replaced it with the handleEventBooking();

• Fixes [CAL-4943] If all information for "confirm" step is provided skip step #18307 (GitHub issue number)
• Fixes CAL-4943 (Linear issue number - should be visible at the bottom of the GitHub issue description)

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.

LOOM LINK: https://www.loom.com/share/2967cdb902fb4945908e17c79bb379b8?sid=88459728-1b9e-46e9-af1a-9168cd8cc0cc

How should this be tested?

You can start by creating event types with varying complexity and check if any URL params are conflicting this direct booking without confirmation.

No ENV vars required to test.

[vercel]

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

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[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 "added functionality to remove the confirm step in creating bookings". 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 • (12/27/24)

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

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

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

"Add community label" took an action on this PR • (12/27/24)

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

[Praashh]

also can you please add a loom recording of the fix @theVedanta 🙏 ?

[theVedanta]

also can you please add a loom recording of the fix @theVedanta 🙏 ?

I've added it in the first comment or the PR description.

[Praashh]

also can you please add a loom recording of the fix @theVedanta 🙏 ?

I've added it in the first comment or the PR description.

Alright, thanks! One thing I wanted to ask is, if someone accidentally clicks the button, it’ll immediately book the meeting. I think it would be better to have a confirmation dialog box or something similar to prevent this.

[theVedanta]

also can you please add a loom recording of the fix @theVedanta 🙏 ?

I've added it in the first comment or the PR description.

Alright, thanks! One thing I wanted to ask is, if someone accidentally clicks the button, it’ll immediately book the meeting. I think it would be better to have a confirmation dialog box or something similar to prevent this.

This has been discussed in the GitHub issue before. Please check the issue once and let me know if a dialog box is required.

[Praashh]

also can you please add a loom recording of the fix @theVedanta 🙏 ?

I've added it in the first comment or the PR description.

Alright, thanks! One thing I wanted to ask is, if someone accidentally clicks the button, it’ll immediately book the meeting. I think it would be better to have a confirmation dialog box or something similar to prevent this.

This has been discussed in the GitHub issue before. Please check the issue once and let me know if a dialog box is required.

yeah, got the answer, thank you 🙏

[Praashh]

Can we have a test case for this feature @theVedanta?

[theVedanta]

Can we have a test case for this feature @theVedanta?

Sure, can you please provide some context and more information on how you want the tescases generaeted?