feat: add more routing forms data

[keithwillcode]

What does this PR do?

• Fixes #XXXX (GitHub issue number)
• Fixes CAL-XXXX (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).
• 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.

How should this be tested?

• Are there environment variables that should be set?
• What are the minimal test data to have?
• What is expected (happy path) to have (input and output)?
• Any other important info that could help to test that PR

Checklist

• I haven't read the contributing guide
• My code doesn't follow the style guidelines of this project
• I haven't commented my code, particularly in hard-to-understand areas
• I haven't checked if my changes generate no new warnings

[zomars]

Taking over this PR

[zomars]

Fixed date formatting and replaced the user name with email as it might a be better identifier:

[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		Oct 25, 2024 1:37am
calcom-web-canary	⬜️ Ignored (Inspect)	Visit Preview		Oct 25, 2024 1:37am

[github-actions]

E2E results are ready!

• Workflow #36030.1 latest results

[zomars]

Nevermind. Tests are breaking. I underestimated the complexity here.

[zomars]

Made a refactor using a presenter pattern to not mess with the buildResponsesForReporting tests and types.

[graphite-app]

Graphite Automations

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

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