Fix azure-keyvault-keys GitHub link

[ghost]

The azure-keyvault-keys GitHub link actually goes to the
azure-keyvault-secrets repository. Fix that and also provide a link to
the azure-keyvault-keys GitHub repository.

[opbld32]

Docs Build status updates of commit 93bcba0:

🕙 Full build: the average full build time is 144 min(s) 21 sec(s), this is based on the last 372 build(s) for this repository.

[opbld31]

Docs Build status updates of commit 93bcba0:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs-ref-services/keyvault-secrets-readme.md	⚠️Warning	View (azure-python)	Details

docs-ref-services/keyvault-secrets-readme.md

• Line 28: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 156: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/about-keys-secrets-and-certificates#key-vault-secrets' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 236: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 237: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[scbedd]

Hey @LabanSkollerDefensify we appreciate the contribution! This readme is updated as part of automation. I have mirrored your update over here to make certain we don't flatten your change when the next release goes out.

[ghost]

@scbedd: Aha. Thank you!