avm-res-network-privateendpoint 0.3.0: breaking changes

Breaking changes listed in the release notes:

• Provider and Terraform requirements: Terraform >= 1.16, < 2.0 and Azure/azapi ~> 2.12 are now required.
• Parent scope: Replace resource_group_name with parent_id, containing the resource group's full Azure resource ID.
• Outputs: The whole-resource resource output has been removed. Use name, resource_id, network_interface_ids, private_ip_addresses, and application_security_group_association_ids instead.
• Role assignments: Remove role_assignment_name_use_random_uuid from module inputs. Existing assignment GUIDs are preserved through the supported migration path.
• DNS zone group ownership: Private DNS zone groups now have an independently managed child-module state address and require the managed migration flag when upgrading an existing configured group.

1. Breaking changes listed in the release notes for 0.3.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-privateendpoint 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.3.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.3.0, set the version argument to it, then run terraform init so that Terraform can update the local code.