Update britive-provisioning-tutorial.md for new UI changes

[sangeetab-britive]

https://elbrus.atlassian.net/browse/PAB-21429

[learn-build-service-prod]

Learn Build status updates of commit afcb670:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/identity/saas-apps/britive-provisioning-tutorial.md	✅Succeeded

For more details, please refer to the build report.

[sangeetab-britive]

@sangeetab-britive please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Britive"

[prmerger-automator]

@sangeetab-britive : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[v-regandowner]

@jeevansd - Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team