avm-res-network-privatednszone 0.6.0: breaking changes

Breaking changes listed in the release notes:

• Root and directly consumed child modules require location when telemetry is enabled (the default). Set a valid Azure region, or explicitly disable telemetry.
• The minimum Azure AzAPI provider version is now 2.12 for the root and child modules.
• Enabled telemetry now creates subscription-scope ARM deployments and requires permissions to manage those deployments. Previous telemetry state entries are retired without destruction, and new telemetry resources enter state.
• The root name output now uses the configured resource name instead of the name returned in the API response.

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-network-privatednszone 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.