Fix Docs to use Global API Key when disabling SSO

[tamires-cloudflare]

This API only accepts Global API authentication; example using token is inaccurate.

Summary

Changing the authentication method on the example to use Global API Key instead of token.

Documentation checklist

• The documentation style guide has been adhered to.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[hyperlint-ai]

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.

---

PR Change Summary

Updated documentation to reflect the correct authentication method for disabling SSO, using Global API Key instead of a token.

• Changed the authentication method in the API example to use Global API Key.
• Removed the use of Bearer token in the cURL command.
• Ensured compliance with the documentation style guide.

Modified Files

• src/content/docs/cloudflare-one/applications/configure-apps/dash-sso-apps.mdx

---

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

[holopin-bot]

Congratulations @tamires-cloudflare, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm9h9dllq72280cl79w3nysr3

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!