avm-res-containerregistry-registry 0.9.0: breaking changes

Breaking changes listed in the release notes:

• Direct users of modules/cache-rule, modules/credential-set and modules/scope-map must now supply a non-null location, including when enable_telemetry=false. Root calls already forward the existing root location.
• Direct modules/scope-map users now require Terraform >= 1.5.0, < 2.0.0 instead of >= 1.3.0, because telemetry uses plantimestamp() and terraform_data. The root, cache-rule and credential-set minima remain >= 1.8.
• Root AzAPI changes from ~> 2.4 to ~> 2.12; cache-rule and credential-set change from >= 2.0, < 3.0 to ~> 2.12; scope-map newly requires AzAPI ~> 2.12. Refresh incompatible lockfiles. Root AzureRM remains >= 4.81.0, < 5.0.0.
• Root and all three children enable subscription-scope deployment telemetry by default. Configure the intended AzAPI subscription and grant appropriate subscription-deployment lifecycle permissions, or disable telemetry. Root enable_telemetry is forwarded to its children; direct child callers must configure their own flag. Deployments contain no workload resources, but add deployment-history and plan-timestamp updates.
• Root ModTM and telemetry-only Random requirements are removed. removed blocks request forgetting the old telemetry resources without destruction; actual historical-state migration was not exercised. Back up state and inspect the upgrade plan. Naming examples still legitimately consume Random through the ModTM-free Naming module.

1. Breaking changes listed in the release notes for 0.9.0: 5. 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-containerregistry-registry 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.9.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.9.0, set the version argument to it, then run terraform init so that Terraform can update the local code.