fix: Zoom integration doesn't follow the zoom app settings for auto-record

[sbsangu]

What does this PR do?

This PR addresses the issue identified in [CAL-3943] where meetings generated via cal.com to our team's Zoom account do not auto-record despite the Zoom app settings being configured to enable auto-recording. This change ensures that meetings created through cal.com adhere to the Zoom app settings for auto-recording.

• Fixes [CAL-3943] Zoom integration doesn't follow the zoom app settings for auto-record #15474 (GitHub issue number)
• Fixes CAL-3943 (Linear issue number)

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
• N/A-I have added or modified automated tests that prove my fix is effective or that my feature works (PRs might be rejected if logical changes are not properly tested)

How should this be tested?

Checklist

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

[vercel]

@sbsangu 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:

Unknown release type "Fix" found in pull request title "Fix: Zoom integration doesn't follow the zoom app settings for auto-record". 

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 community label" took an action on this PR • (06/18/24)

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

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

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

[sean-brydon]

Nice job - lets fix eslint errors + can we try add the default password into the meeting as i think we can do this now as we have the settings for the users new events

[sbsangu]

@sean-brydon does this now resolve the issue #15474 ?