fix: skip confirm step followup

[SomayChauhan]

What does this PR do?

This PR fixes the following issues in the Booker flow when skipping the confirmation step:

1. Ensuring Users Are Notified of Submission Errors

   • Previously, if a user skipped the confirmation step and an error occurred during submission, there was no notification.
   • This PR introduces a toast notification to alert users when a submission error happens.
   • Demo: [Loom Video](https://www.loom.com/share/49dc3c7c12284ffca6c9ddfb16317eba?sid=c18adb48-16b4-4edc-9198-fabf83eedae1)

2. Fixing the Double Click Issue on the Confirm Button

   • Before, users had to click the Confirm button twice in the Booker Atom for the submission to proceed.

   • This PR resolves the issue, ensuring a single click properly triggers the submission.

   • before: https://github.com/user-attachments/assets/d3d5909b-469b-4802-94be-5d0eac408ece

     • after: https://www.loom.com/share/0f19c97bc7a24cd3886e5cc6e3c7fc38?sid=f2bdf511-8dd5-4562-a725-0aa83278e176

3. When a user clicks on a new timeslot, any previously displayed "Confirm" button should be hidden.
   This ensures only one confirm button is visible at a time, improving clarity and avoiding confusion.

4. Clicking on a timeslot that already has the "Confirm" button visible should hide the button instead of confirming the booking.
   This provides a more intuitive and user-friendly experience, aligning with natural user behavior. Since our "Confirm" button is large and clearly visible, it shouldn't be a problem

• https://www.loom.com/share/160e86ce85e645269393913d3caaddf7?sid=73eaeeb2-97e1-4ea9-9126-70cb53ef8b09

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.

[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 "Followup/skip confirm step". 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 • (02/04/25)

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

"Add platform team as reviewer" took an action on this PR • (02/04/25)

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
cal-com-ui-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 7, 2025 4:23am

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
cal	⬜️ Ignored (Inspect)	Visit Preview		Feb 7, 2025 4:23am
calcom-web-canary	⬜️ Ignored (Inspect)	Visit Preview		Feb 7, 2025 4:23am

[github-actions]

E2E results are ready!

• Workflow #46691.1 latest results