Azure *-infrastructure workflows sometimes fail

*-infrastructure Azure workflows sometimes fail with:

```text
Error: Provider produced inconsistent result after apply
When applying changes to azurerm_portal_dashboard.deployment, provider "provider[\"registry.terraform.io/hashicorp/azurerm\"]" produced an unexpected new value: Root object was present, but now absent.

This is a bug in the provider, which should be reported in the provider's│own issue tracker.
```

This specific error—"Root object was present, but now absent"—is a notorious Terraform quirk usually triggered when the Azure API returns a 404 Not Found immediately after Terraform thinks it successfully created or updated a resource.

For the azurerm_portal_dashboard resource, this almost always happens because of an eventual consistency delay in Azure's global dashboard service. Terraform sends the "Create" command, Azure says "Accepted," but when Terraform immediately tries to "Read" the dashboard back to confirm its state, the dashboard hasn't finished replicating across Azure's internal systems yet.