avm-res-network-virtualnetwork 0.23.0: breaking changes

Breaking changes listed in the release notes:

• Standalone modules/subnet and modules/peering now enable telemetry by default and require a non-null location when telemetry is enabled. Existing direct callers must supply location or explicitly set enable_telemetry = false. The root module passes its existing location to these children.
• Enabled telemetry now creates Azure subscription-scope deployments through AzAPI, including for the root module and enabled children. Identities must have the necessary subscription-scope deployment permissions; alternatively disable telemetry. Terraform state forgets legacy ModTM telemetry and telemetry UUID objects without destroying them and tracks the new telemetry deployment resources.

1. Breaking changes listed in the release notes for 0.23.0: 2. 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-virtualnetwork 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.23.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.23.0, set the version argument to it, then run terraform init so that Terraform can update the local code.