Kusto returns `Terminal` rather than `Failed`

👋

When provisioning a Kusto Cluster via our Test Suite - we've noticed an error being returned from the API:

> Code="RequestConflict"
> Message="Cannot modify resource with id '/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/acctestRG-191216063251381036/providers/Microsoft.Kusto/Clusters/acctestkcdluqfx' because the resource entity provisioning state is not terminal. Please wait for the provisioning state to become terminal and then retry the request."

Every other Azure API I'm aware of returns resources which have finished provisioning with an error as `Failed` - however it appears that the Kusto API returns this as `terminal`. Would it be possible to get this fixed so that downstream clients can handle the cases appropriately?

Thanks!

Start by locating the Kusto Cluster provisioning-state schema or response definition in this repository and compare its terminal and failed values with the reported API behavior. Confirm the intended mapping for a failed provisioning response, then validate that the published REST specification exposes Failed rather than Terminal so downstream clients can distinguish the case.

Written by the indexing model from the issue text.