[MOVED] feat(azure): Add Key Vault key inspection

[nevzheng]

Moved to Gravitino Enterprise: datastrato/gravitino-enterprise#903. Apache issue #12131 is now limited to the provider-neutral API/SPI and named-source routing.

What changes were proposed in this pull request?

Add an Azure Key Vault provider using the official Azure SDK and DefaultAzureCredential. It validates full key URLs against the configured vault, supports latest or pinned versions, and normalizes effective enabled state and wrapKey/unwrapKey capabilities.

Why are the changes needed?

Azure key URLs, versions, validity windows, and operations require provider-specific interpretation behind the common KMS contract.

This work is now tracked in datastrato/gravitino-enterprise#903. The Apache OSS foundation remains #12132 and #12133.

Does this PR introduce any user-facing change?

Yes. It adds the azure-key-vault source type and its configuration properties.

How was this patch tested?

• ./gradlew :bundles:azure:test -PskipITs

Migration

• Enterprise epic: datastrato/gravitino-enterprise#899
• Enterprise PR: datastrato/gravitino-enterprise#903
• OSS foundation: [EPIC] Add provider-neutral KMS interfaces #12131, [#12131] feat(kms): Define key inspection API #12132, and [#12131] feat(kms): Configure and route named sources #12133

[nevzheng]

Hi @roryqi and @lasdf1234 — please review this KMS API change (6/11). Previous: #12136. Next: #12138. Epic: #12131.

[nevzheng]

Moved to datastrato/gravitino-enterprise#903 under enterprise epic #899. Apache OSS scope remains #12132 and #12133 under #12131.