fix: how-to-setup-api-in-a-local-instance.mdx in docs with correction after api-v2

[sathuli2710]

After the implementation of api-v2, some of the documents are not yet updated and could you make developers spend too much time on finding these things.

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)
• This is an issue I noticed while going through the docs.
• This changes some text in the documentation for how to setup api in local instance page

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.
• [N/A] 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? No
• What are the minimal test data to have? NA
• What is expected (happy path) to have (input and output)? Check the edited docs page after update under the link https://cal.com/docs/developing/guides/api/how-to-setup-api-in-a-local-instance
• Any other important info that could help to test that PR

Checklist

• I haven't checked if my changes generate no new warnings

[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 "Updating how-to-setup-api-in-a-local-instance.mdx in docs with correction after api-v2". 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

[vercel]

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

A member of the Team first needs to authorize it.

[graphite-app]

Graphite Automations

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

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

"Add community label" took an action on this PR • (11/15/24)

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

"Add ready-for-e2e label" took an action on this PR • (11/16/24)

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

[github-actions]

E2E results are ready!

• Workflow #38216.1 latest results