Update Microsoft.Azure.KeyVault 3.0.99-Private to Azure.Security.KeyVault

Our build pipeline is using `azure-sdk-tools` repo to generate the json file for APIView https://github.com/Azure/azure-sdk-tools/tree/main/src/swift.

Since it's checking out the complete repo, compliance scan is detecting that the Microsoft.Azure.KeyVault nuget package used in the repo should be updated to Azure.Security.KeyVault package to receive further updates.

`This package is deprecated and will receive no further updates, including security updates. Users need to migrate to an Azure.Security.KeyVault package. Depending on what functionality of Key Vault is being used (Keys, Secrets, or Certificates), users need to migrate to one of the following packages: - Secrets: https://www.nuget.org/packages/Azure.Security.KeyVault.Secrets ([Migration guide](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/keyvault/Azure.Security.KeyVault.Secrets/MigrationGuide.md)) - Keys and cryptography: https://www.nuget.org/packages/Azure.Security.KeyVault.Keys ([Migration guide](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/keyvault/Azure.Security.KeyVault.Keys/MigrationGuide.md)) - Certificates: https://www.nuget.org/packages/Azure.Security.KeyVault.Certificates ([Migration guide](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/keyvault/Azure.Security.KeyVault.Certificates/MigrationGuide.md)) Managing SAS tokens using Key Vault is not supported. Teams are encouraged to use IAM instead.`