fix: Handle more dry-run cases

[hariombalhara]

What does this PR do?

• Workflow
• Seated Events
• Webhooks

Adds Dry Run success page that we can fill with more details later - Loom

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.
• Not Needed - I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

Try doing the booking

[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 "Handle more dry-run cases". 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/20/24)

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 ↗︎

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
cal	⬜️ Ignored (Inspect)	Visit Preview		Dec 20, 2024 9:32am
calcom-web-canary	⬜️ Ignored (Inspect)	Visit Preview		Dec 20, 2024 9:32am

[github-actions]

E2E results are ready!

• Workflow #42048.1 latest results

[hariombalhara]

Moved all args to single object as I needed to add a new one

[PeerRich]

lets actually show the test data as a result. i like it

Suggested change

	{/* <div className="border-subtle text-default mt-8 grid grid-cols-3 border-t pt-8 text-left">
	<div className="font-medium">{t("what")}</div>
	<div className="col-span-2 mb-6">{sampleBookingInfo.title}</div>
	<div className="font-medium">{t("when")}</div>
	<div className="col-span-2 mb-6">{new Date(sampleBookingInfo.startTime).toLocaleString()}</div>
	<div className="font-medium">{t("who")}</div>
	<div className="col-span-2 mb-6">
	<div className="mb-3">
	<div>
	<span className="mr-2">{sampleBookingInfo.user.name}</span>
	<Badge variant="blue">{t("Host")}</Badge>
	</div>
	<p className="text-default">{sampleBookingInfo.user.email}</p>
	</div>
	<div>
	<p>{sampleBookingInfo.attendees[0].name}</p>
	<p>{sampleBookingInfo.attendees[0].email}</p>
	</div>
	</div>
	<div className="font-medium">{t("where")}</div>
	<div className="col-span-2 mb-6">{sampleBookingInfo.location}</div>
	</div> */}
	<div className="border-subtle text-default mt-8 grid grid-cols-3 border-t pt-8 text-left">
	<div className="font-medium">{t("what")}</div>
	<div className="col-span-2 mb-6">{sampleBookingInfo.title}</div>
	<div className="font-medium">{t("when")}</div>
	<div className="col-span-2 mb-6">{new Date(sampleBookingInfo.startTime).toLocaleString()}</div>
	<div className="font-medium">{t("who")}</div>
	<div className="col-span-2 mb-6">
	<div className="mb-3">
	<div>
	<span className="mr-2">{sampleBookingInfo.user.name}</span>
	<Badge variant="blue">{t("Host")}</Badge>
	</div>
	<p className="text-default">{sampleBookingInfo.user.email}</p>
	</div>
	<div>
	<p>{sampleBookingInfo.attendees[0].name}</p>
	<p>{sampleBookingInfo.attendees[0].email}</p>
	</div>
	</div>
	<div className="font-medium">{t("where")}</div>
	<div className="col-span-2 mb-6">{sampleBookingInfo.location}</div>
	</div>

[PeerRich]

would actually need the actual dryRun results here, not static

[hariombalhara]

Yeah, thats planned for a followup as it has other dry run fixes as well.