avm-res-network-loadbalancer 0.6.0: breaking changes

Breaking changes listed in the release notes:

• Read the v0.5.0 upgrade guide before upgrading. This is not a drop-in provider replacement.
• Requirements: Terraform >= 1.16, < 2.0 and effective AzAPI provider minimum 2.13.
• Parent scope: replace resource_group_name with the existing resource group's parent_id.
• Public IP ownership: bundled public IP creation and extension management are removed. Manage and adopt existing public IPs and their extensions in the consumer configuration, then supply their resource IDs.
• Native NIC associations: backend_address_pool_network_interfaces is removed. Manage complete native membership lists exclusively through the NIC/compute owner, using the module's keyed backend pool IDs.
• Backend pool defaults: omitted or null backend_address_type now means "NIC". Explicit IP pools must select "IP"; Global regional-frontend pools must select "Frontend". These modes do not automatically convert existing pools.
• Diagnostic settings: replace legacy category arrays with canonical logs and metrics objects.
• Outputs: replace removed whole-resource objects with discrete IDs, keyed child-ID maps and name. Legacy AzureRM object shapes are not preserved.
• Authoritative collections: configure all intended children and explicit members; omitted entries can be removed.

1. Breaking changes listed in the release notes for 0.6.0: 9. 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-loadbalancer 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.