Kusto Cluster API silently changes the specified `zones` during creation

The Kusto Cluster API silently changes the specified `zones` during creation, which happens systematically, at least for version 2021-08-27.

## Example

x-ms-correlation-request-id: e1138e9e-b71d-0ab8-14b7-3b24eea44813
x-ms-request-id: a4ea9cf3-a428-4fe9-b47b-40f565140bb2

The create request & response

```
PUT /subscriptions/****/resourceGroups/mgd-kusto-cluster-rg/providers/Microsoft.Kusto/clusters/mgdkustocluster?api-version=2021-08-27

{..., "zones":["2","1"]}

RESPONSE

{..., "zones":["2","1"]}
```

Then after waiting the LRO to finish and call a GET on it:

```
GET /subscriptions/****/resourceGroups/mgd-kusto-cluster-rg/providers/Microsoft.Kusto/clusters/mgdkustocluster?api-version=2021-08-27

RESPONSE

{..., "zones":["3","1"]}
```

## Reference

https://github.com/hashicorp/terraform-provider-azurerm/issues/17461

Start by locating the Microsoft.Kusto cluster specification for API version 2021-08-27 and compare the documented `zones` property with the create and subsequent GET responses described here. Determine whether the specification can represent the observed behavior and document the evidence needed to consider the issue resolved.

Written by the indexing model from the issue text.