destroy managed service fabric meeting interlock

when we destroy managed service fabric cluster, it will destroy primary node type before destroy cluster. But when destroy primary node type, it reports below error.

│ RESPONSE 400: 400 Bad Request
│ ERROR CODE: InvalidParameter
│ --------------------------------------------------------------------------------
│ {
│ "error": {
│ "code": "InvalidParameter",
│ "message": "Cluster must have at least one active primary node type."
│ }
│ }

So we can not destroy managed service fabric cluster, because of interlock.

Reproduce destruction of an Azure Service Fabric cluster and observe whether the primary node type is destroyed before the cluster. Inspect the provider's managed Service Fabric resource handling and its destroy ordering. Done means the cluster can be destroyed without the Azure "at least one active primary node type" error.

Written by the indexing model from the issue text.