resource/kubernetes_cluster: Fix missing forceNew on service principal fields

[lawrencegripper]

Repro using the current provider:

1. Create a cluster
2. Change the Service Principal used
3. See error:

• azurerm_kubernetes_cluster.aks: containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="PropertyChangeNotAllowed" Message="Changing property 'servicePrincipalProfile.clientId' is not allowed." Target="servicePrincipalProfile.clientId"

This PR moves the SP properties to ForceNew to fix this issue and force a new cluster when changes are made.

[tombuildsstuff]

LGTM - thanks for this 👍

[tombuildsstuff]

hey @lawrencegripper

Just to let you know that we've just shipped support for this as a part of v1.13.0 of the AzureRM Provider :)

Thanks!

[hazzik]

This does not have any effect because the client_secret is not retrieved from the environment nor stored in a state file.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!