ClientEncryption: Adds the use of Azure.Core interfaces in public surface

[abhijitpai]

Description

Use interfaces from Azure.Core.Cryptography for customers to provide the implementation used to wrap/unwrap the data encryption key instead of the existing custom wrapper interfaces created over Microsoft.Data.Encryption.Cryptography. This allows using the Azure.Security.KeyVault.Keys implementation for CMKs in Azure Key Vault and we no longer need the MDE specific Microsoft.Data.Encryption.AzureKeyVaultProvider.

Type of change

• [] Breaking change (fix or feature that would cause existing functionality to not work as expected)

[github-actions]

Please follow the required format: "[Internal] Category: (Adds|Fixes|Refactors|Removes) Description"

Internal should be used for PRs that have no customer impact. This flag is used to help generate the changelog to know which PRs should be included. Examples:
Diagnostics: Adds GetElapsedClientLatency to CosmosDiagnostics
PartitionKey: Fixes null reference when using default(PartitionKey)
[v4] Client Encryption: Refactors code to external project
[Internal] Query: Adds code generator for CosmosNumbers for easy additions in the future.

All good!

[simplynaveen20]

LGTM , Thanks @abhijitpai .
Two thing we noticed and we will notify the core team , that the resolver/builder design is not ideal , it is creating KeyEncryptionKeyClient every time even for same key via resolver resolve/build method.