Microsoft Entra ID name update

[danycontre]

Overview/Summary

Replace this with a brief description of what this Pull Request fixes, changes, etc.

This PR fixes/adds/changes/removes

1. Updating Azure AD to Microsoft Entra ID
2. Updating AAD to EntraID
3. Updating Azure AD Domain Services to Microsoft Entra Domain Services

Breaking Changes

1. Replace me
2. Replace me

Testing Evidence

Replace this with any testing evidence to show that your Pull Request works/fixes as described and planned (include screenshots, if appropriate).

As part of this Pull Request I have

• [ ] Read the Contribution Guide and ensured this PR is compliant with the guide
• [ ] Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
• [ ] Checked for duplicate Pull Requests
• [ ] Associated it with relevant GitHub Issues
• [ ] (AVD LZA Team Only) Associated it with relevant ADO Items
• [ ] Ensured my code/branch is up-to-date with the latest changes in the main branch
• [ ] Performed testing and provided evidence.
• [ ] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Docs etc.)

[danycontre]

Just a quick observation, for the CARML modules, unless you've done other editing in the modules to make them custom, I'd say revert those specific changes and let this be an "upstream" problem that is presumably fixed with a future release of their modules. Just adjust your own code, not their modules. Future of CARML is weird anyhow with AVM coming up -- but that's a whole other topic :)

Agree, we will be updating CARML modules to AVM soon, but to your point, yes, we made local edits to the CARML modules, so they work in our use case.

[danycontre]

Updated code merged.

cc: @moisesjgomez @ckittel @swathibhat1