Update provision-use-jit.md for Azure, Google, and Okta

[dtsong-harness]

Add guidance to end-users on how to confirm that JIT is properly configured for their SSO provider with examples covering Azure, Google, and Okta.

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.

Description

• Please describe your changes: __________________________________
• Jira/GitHub Issue numbers (if any): ______________________________
• Preview links/images (Internal contributors only): __________________

PR lifecycle

We aim to merge PRs within one week or less, but delays happen sometimes.

If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.

PRs must meet these requirements to be merged:

• Successful preview build.
• Code owner review.
• No merge conflicts.
• Release notes/new features docs: Feature/version released to at least one prod environment.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[bot-gitexp-user]

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://69bc766c9a254cbac47efb2d--harness-developer.netlify.app