Redeploying a failing Container Function App results in conflict.

**Which trigger/binding are you using?**
EventhubTrigger
**Which language are you using?**
Rust and a custom handler
**Provide resource details**
unable to provide this.

**Expected behavior**
I should be able to redeploy the failing Azure Container App Function using Terraform without encountering any conflict or error.

**Actual behavior**
Attempting to redeploy results in a conflict with the automatically created resource group:

**Logs**
```json
{
"error": {
"code": "FailedIdentityOperation",
"message": "Identity operation for resource '/subscriptions/mysubscription/resourceGroups/mscreatedresourcegroup_somerandomid/providers/Microsoft.App/containerApps/funcname' failed with error 'Failed to perform resource identity operation. Status: 'Conflict'. Response: '{\"error\":{\"code\":\"Conflict\",\"message\":\"Request specified that resource '/subscriptions/mysubscription/resourcegroups/mscreatedresourcegroup_somerandomid/providers/Microsoft.App/containerApps/funcname' is new, but resource already exists. This may be due to a pending delete operation, try again later.\"}'"
}
}
```
**Additional context**
A similar issue is this: https://github.com/Azure/azure-functions-on-container-apps/issues/40

Start by reviewing the Terraform deployment path for an Azure Container Function using an EventhubTrigger and Rust custom handler, then compare the redeployment failure with issue #40. Reproduce the failing redeploy and inspect the reported FailedIdentityOperation conflict; done means the failing app can be redeployed without a resource conflict.

Written by the indexing model from the issue text.