Update helm chart to support azure key vault specific certificate secret

[nisan-abeywickrama]

Purpose

This pull request introduces significant improvements to Azure Key Vault integration for Helm deployments of APK components. The changes standardize and streamline how secrets and TLS certificates are managed and mounted for Azure, update secret references and naming conventions, and enhance support for Azure-specific configurations across multiple components.

Approach

Azure Key Vault Integration and Secret Handling

• Added explicit support for Azure as a secret provider, with conditional logic in deployment templates to mount secrets and TLS certificates from Azure Key Vault for all major components (adapter, common-controller, gateway-runtime, ratelimiter). This includes new volume mounts and secret references for Azure-provided TLS assets.
• Updated the secret-provider-azure.yaml template to add new secret definitions (apk-server-tls, enforcer-jwks-tls) and refactored object aliases and references to align with Azure Key Vault naming and structure. This also includes changes to parameter names (e.g., tenantId instead of azureTenantID).
  Helm Values and Configuration
• Extended values.yaml to include Azure-specific configuration fields for Key Vault and new secret references (apkServerKey, apkServerCert, etc.), improving clarity and flexibility for Azure deployments.

Versioning

• Bumped the Helm chart version from 1.3.0-9 to 1.3.0-10 to reflect these updates.

Conditional Logic and Volume Mounts

• Added Azure-specific conditional blocks in deployment templates to ensure correct mounting of secrets and certificates only when Azure is selected as the provider, reducing the risk of misconfiguration and improving maintainability.