avm-res-web-site 0.23.0: breaking changes

Breaking changes listed in the release notes:

• Logic App Node.js default: Logic Apps that do not set WEBSITE_NODE_DEFAULT_VERSION move from Node.js ~18 to ~22. Validate workflows before applying, or set logic_app_node_version = "~18" to retain the old runtime. (#344)
• Logic App worker runtime: The module now sends Microsoft's documented FUNCTIONS_WORKER_RUNTIME = "dotnet" instead of "node". Microsoft says this should not affect workflow execution. To retain the old value, set app_settings = { FUNCTIONS_WORKER_RUNTIME = "node" } using that casing. (#379)
• Removed outputs: Unused whole-resource outputs were removed from the certificate and configuration submodules. The root deployment_slot_locks, resource_lock, and resource_private_endpoints outputs were removed, and deployment_slots now exposes only each slot's name and resource_id. The root resource and private_endpoints compatibility outputs remain. Replace references with the available discrete outputs. (#369)
• Output sensitivity: custom_domain_verification_id is now sensitive. Mark downstream outputs as sensitive, or use nonsensitive() when publishing it to the public asuid.<hostname> DNS TXT record. Resource and managed-identity IDs are no longer marked sensitive; existing downstream sensitive = true declarations remain valid. (#371)
• Explicit null collection inputs: always_ready, backup, connection_strings, site_config, slots_storage_shares_to_mount_sensitive_values, sticky_settings, and storage_shares_to_mount now treat explicit null as absent and use their declared defaults. Remove explicit null assignments when upgrading. retry = null remains supported and continues to disable retries. (#374)
• Flex Consumption app settings: New FC1 deployments no longer receive module-supplied FUNCTIONS_EXTENSION_VERSION or WEBSITE_CONTENTSHARE. Existing apps may retain previously written values because the underlying update resource merges settings; FC1 ignores them. Explicit caller-supplied app settings still pass through. (#380)

1. Breaking changes listed in the release notes for 0.23.0: 6. 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-web-site 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.