avm-res-network-routetable 0.6.0: breaking changes

Breaking changes listed in the release notes:

• Direct users of modules/route must now supply a non-null real Azure location even when enable_telemetry=false. Root callers already supply location; the root forwards it and enable_telemetry to each route child. No new required root input is added.
• Default-enabled telemetry now creates empty Incremental subscription deployments for the root and every instantiated non-legacy route child. Subscription deployment-management permissions are required; resource-group-only routing permissions may be insufficient. Owner is not specifically required. Configure the intended AzAPI subscription or explicitly disable telemetry. Expect additional deployment-history records per child and plan-timestamp updates. Existing routes_legacy_mode selection is unchanged.
• AzAPI now requires~>2.12 instead of~>2.4 in root and direct route child. Terraform>=1.9,<2.0 and AzureRM~>4.0 remain unchanged. Refresh provider locks as appropriate.
• ModTM and telemetry-only root Random requirements are removed. Non-destructive removed blocks request forgetting old root telemetry resources. Workload addresses and map keys are preserved, but an actual historical-state upgrade has not been exercised; back up state and inspect the plan.
• Route-table/route request bodies, route outputs, subnet associations, locks and role assignments retain their existing contract. Examples use exact certified Naming0.2.0 and legacy Regions0.8.2.

1. Breaking changes listed in the release notes for 0.6.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-network-routetable 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.