avm-res-resources-resourcegroup 0.5.0: breaking changes

Breaking changes listed in the release notes:

• Back up state and inspect the complete plan before applying. These changes are not a guarantee of a safe or replacement-free upgrade.
• Resource-group state now uses a counted AzAPI address. The move chain is azurerm_resource_group.this → azapi_resource.this → azapi_resource.this[0]; the last step also covers v0.4.0's unkeyed AzAPI address. Cross-provider conversion requires supported provider versions and usable Azure resource IDs. If conversion cannot be performed, explicit migration or import may be required.
• The new ignore_tag_changes input defaults to false. Do not toggle it on an existing group without a reviewed migration: switching resource definitions can plan a delete and create of the resource group, with potential loss of its contents.
• Lock configuration now includes notes = null; v0.4.0 omitted notes and older AzureRM-based versions supplied notes. Azure's handling of the explicit null has not been verified. Review existing notes and the plan.
• For AzureRM-era role assignments, explicitly set role_assignments[*].name to the existing assignment GUID before migration and inspect the plan; otherwise a new UUID can result in a different assignment name.
• The full resource output changes shape: a resource attribute is added (null in the default synthetic fixture). With ignore_tag_changes = true, reported tags are null. Consumers relying on the exact output object should review their use.
• AzAPI changes from ~> 2.4 to ~> 2.12; Terraform remains >= 1.9, < 2.0. Interfaces changes from 0.6.0 to 0.10.0. Active ModTM telemetry is replaced by subscription-scope AzAPI deployments. When telemetry is enabled, deployment read, write and delete permissions are required at subscription scope. Old telemetry state may need its old providers for a final initialization; removed telemetry resources are forgotten without destruction. Telemetry can be disabled with enable_telemetry = false.
• Offline synthetic-state/mock-provider plans covered the v0.4.0 and older AzureRM address chains; they do not prove live Azure behavior or all provider/Terraform version combinations. No live upgrade was performed.

1. Breaking changes listed in the release notes for 0.5.0: 8. 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-resources-resourcegroup 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.5.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.5.0, set the version argument to it, then run terraform init so that Terraform can update the local code.