Updated Key Vault RBAC permission

[bolt-io]

This include appears in the following doc: https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-properties?tabs=azure-portal#configure-access-to-key-vault

This refers to adding Named Values to API Management using Key Vault. As Named Values in key vault can only be secrets the correct RBAC permissions is Key Vault Secrets User and not Key Vault Certificate User

[prmerger-automator]

@bolt-io : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit b13f43d:

✅ Validation status: passed

File	Status	Preview URL	Details
includes/api-management-key-vault-access.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[ttorble]

@dlepow

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

[dlepow]

@bolt-io - You are correct and thank you for pointing out the error! Unfortunately the correction you made is in a file that is shared in several other contexts, including for certificates (where the existing permissions remain correct, I believe). I will pull your commit into a separate PR to make the correction in the location for named values only. After the correction is published, I will update and close this PR. Cheers.