chore(deps): update terraform azuread to v2.53.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
azuread (source)	required_provider	minor	2.50.0 -> 2.53.1

---

Release Notes

hashicorp/terraform-provider-azuread (azuread)

v2.53.1

Compare Source

BUG FIXES:

• azuread_application - export the password attribute only when it is set in configuration, to prevent marking existing resources as sensitive (#​1422)

v2.53.0

Compare Source

ENHANCEMENTS:

• azuread_application - support for the password block (#​1389)

BUG FIXES:

• azuread_claims_mapping_policy - set the correct timeouts for this resource (#​1419)
• azuread_service_principal_claims_mapping_policy_assignment - set the correct timeouts for this resource (#​1419)
• azuread_synchronization_secret - set the correct timeouts for this resource (#​1419)

v2.52.0

Compare Source

BUG FIXES:

• azuread_application - fix a bug that could prevent the ignore_changes lifecycle argument from working for the app_role, oauth2_permission_scope, identifier_uris, optional_claims, and required_resource_access properties (#​1403)
• azuread_application - add a workaround for an API bug when instantiating an application from template using the template_id property (#​1406)

v2.51.0

Compare Source

ENHANCEMENTS:

• data.azuread_users - support for the mails property (#​1400)

BUG FIXES:

• azuread_access_package_assignment_policy - fix a bug preventing removal of the assignment_review_settings block (#​1394)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Improvements

1. Pin Major and Minor Versions Explicitly:
   Although version 2.53.1 is specified, it is still good practice to specify a version constraint that explicitly pins the major and minor versions while allowing patch-level updates. For example:
   hcl
   version = "~> 2.53.0"

   This ensures compatibility with future patch releases without unintentionally upgrading to a new minor or major version, which could introduce breaking changes.
   
   

2. Add a Version Comment:
   Adding a brief comment explaining why the provider version was updated can serve as documentation for future maintainers. For example:

   # Updated provider to 2.53.1 to address compatibility with XYZ feature.
   version = \"~> 2.53.0\"

3. Use a Terraform Lock File:
   Ensure that a terraform.lock.hcl file exists and is checked into version control. This file ensures consistent provider versions across environments and prevents unexpected drift. If it's missing, run terraform providers lock to generate it.

4. Environmental Cost and Carbon Impact:
   Upgrading to a newer version of the AzureAD provider may add features that increase resource provisioning capabilities. Regularly conduct cost reviews to make sure deployed resources remain optimized. Carbon impact is indirectly affected by changes in resource use—ensure optimized configurations to reduce emissions.

5. Monitor Provider Changelog:
   Verify that all changes in the provider between 2.50.0 and 2.53.1 are assessed and do not introduce breaking changes or security risks. Specifically, review the AzureAD provider changelog for relevant updates.