Fix EncryptionConfiguration JSON unmarshaling case sensitivity

[matthewyuh246]

Purpose

Fixes #25725

Fixes EncryptionConfiguration unmarshaling failure when parsing actual Azure Data Factory REST API responses.

Issue

The EncryptionConfiguration struct fails to unmarshal JSON responses from the Azure Data Factory REST API due to case sensitivity mismatch in field names.

Current Behavior:

• Azure Data Factory REST API returns encryption properties with PascalCase: KeyName, VaultBaseUrl, KeyVersion
• SDK's UnmarshalJSON expects camelCase: keyName, vaultBaseUrl, keyVersion
• Result: Encryption configuration fields remain nil after unmarshaling, even when CMK is configured

Expected Behavior:
The SDK should correctly unmarshal encryption configuration from API responses regardless of field name casing.

Root Cause

Mismatch between documentation and actual API:

• Microsoft documentation specifies: keyName, vaultBaseUrl (camelCase)
  • https://learn.microsoft.com/en-us/azure/templates/microsoft.datafactory/factories
• Actual API returns: KeyName, VaultBaseUrl (PascalCase)

Changes

Updated EncryptionConfiguration.UnmarshalJSON in models_serde.go to accept both PascalCase and camelCase variants:

case "keyName", "KeyName":
    err = unpopulate(val, "KeyName", &e.KeyName)
case "keyVersion", "KeyVersion":
    err = unpopulate(val, "KeyVersion", &e.KeyVersion)
case "vaultBaseUrl", "VaultBaseUrl":
    err = unpopulate(val, "VaultBaseURL", &e.VaultBaseURL)

Evidence

REST API Response (verified with az rest):

{
  "properties": {
    "encryption": {
      "KeyName": "my-cmk-key",
      "VaultBaseUrl": "https://my-keyvault.vault.azure.com",
      "KeyVersion": "abc123..."
    }
  }
}

Testing

Tested with real Azure Data Factory instances configured with customer-managed keys. After this change, encryption configuration fields are correctly populated.

Note About Generated Code

This is a fix for generated code. I understand this file is managed by the codegen framework. The root cause may be:

1. Incorrect Swagger spec (should specify PascalCase to match actual API)
2. Azure API inconsistency (should return camelCase as documented)

I'm willing to help fix the proper source (Swagger spec or autorest template) if maintainers can provide guidance on the correct approach.

---

Checklist

• The purpose of this PR is explained in this or a referenced issue.
• The PR does not update generated files.
  • Note: This PR intentionally modifies models_serde.go (a generated file) as a temporary fix for a real-world API compatibility issue. Guidance on the proper long-term solution would be appreciated.
• Tests are included and/or updated for code changes.
  • Note: Based on the repository pattern, models_serde.go typically doesn't have dedicated unit tests.
• Updates to module CHANGELOG.md are included.
  • TODO: Will add if this approach is acceptable.
• MIT license headers are included in each file.
  • Existing file modification, headers already present.

[github-actions]

Thank you for your contribution @matthewyuh246! We will review the pull request and get back to you soon.