avm-res-managedidentity-userassignedidentity 0.6.0: breaking changes

Breaking changes listed in the release notes:

• Rename role_assignments to outbound_role_assignments in every module call; the old argument is no longer accepted. Preserve the existing map keys and values. These remain outbound grants to the created identity at each supplied scope, not grants to other principals on the identity. The resource block remains azurerm_role_assignment.this, so the input rename alone does not require state moves.
• Outbound role assignment description is now applied instead of ignored. AzureRM treats description changes as replacement, so existing non-null descriptions can replace assignments on upgrade. Inspect the plan for resulting access changes. Other role attributes and their existing null defaults remain unchanged.
• enable_telemetry remains true by default. Enabled telemetry creates an empty Incremental Microsoft.Resources/deployments resource at the AzAPI provider subscription, using the existing required real region. Subscription deployment-management permissions are required; resource-group-only permissions may be insufficient. Owner is not specifically required. Configure the intended AzAPI subscription or set enable_telemetry=false. Deployment-history records and plan-timestamp updates are new behavior.
• ModTM and telemetry-only root random requirements are removed. removed blocks with destroy=false request forgetting the old telemetry resources without destruction. Workload addresses are preserved; historical-state migration has not been exercised. Back up state and inspect the upgrade plan, especially outbound assignment descriptions, before applying.

1. Breaking changes listed in the release notes for 0.6.0: 4. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.
2. Check the version argument of the module block that installs avm-res-managedidentity-userassignedidentity from the Terraform Registry. Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.6.0 can bring in this release. A module block with no version argument defaults to the latest version available from the source.
3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.
4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.
5. To adopt 0.6.0, set the version argument to it, then run terraform init so that Terraform can update the local code.