avm-res-cognitiveservices-account 0.12.0: breaking changes

Breaking changes listed in the release notes:

• AzAPI now requires ~> 2.12 (previously ~> 2.5).
• Enabled telemetry creates empty subscription-scoped Azure deployments and requires Microsoft.Resources/deployments/read, write, and delete permissions at the active subscription. Set enable_telemetry = false to disable these deployments.
• Direct callers of modules/deployment and modules/rai_policy must supply location when telemetry is enabled. The parent module forwards its location and telemetry opt-out automatically.
• Previously ignored private endpoint fields are now honored. An explicit role-assignment name can replace its assignment; non-default subresource names can change generated endpoint/NIC/connection names and replace resources. Lock notes and IP member names are now sent to ARM. Review the plan before upgrading.
• Deployment and RAI-policy tags supplied per item now take effect; omitted/null tags retain provider defaults and do not inherit account tags.
• The private-endpoint example replaces legacy VNet module 5.0.1 with AVM VNet 0.23.0, changing example VNet/subnet state addresses. Use fresh disposable example infrastructure or explicitly review and migrate existing example state before applying.
• Legacy telemetry state is forgotten with destroy = false. Terraform can still require the retired providers during the first initialization of an existing state.

1. Breaking changes listed in the release notes for 0.12.0: 7. 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-cognitiveservices-account 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.12.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.12.0, set the version argument to it, then run terraform init so that Terraform can update the local code.