Updating Microsoft Defender for Endpoints to use new initiative

[Springstone]

Overview/Summary

This pull request introduces significant changes to the eslzArm/eslzArm.json and docs/wiki/Whats-new.md files. The main changes are the deprecation of certain policies and the introduction of new ones, as well as the addition of a new initiative for Microsoft Defender for Endpoints. In addition, there are some adjustments in the eslzArm/eslzArm.json file to accommodate these new policies and initiatives.

Policy changes:

• docs/wiki/Whats-new.md: Deprecated the custom policy "Storage Account set to minimum TLS and Secure transfer should be enabled" and replaced it with two built-in policies. Also deprecated the "Deploy-EncryptTransit" initiative and superseded it with "Deploy-EncryptTransit_20240509". Added a new custom policy "Deploy-Private-DNS-Generic" and a new initiative for Microsoft Defender for Endpoints.

Adjustments in eslzArm/eslzArm.json:

• Added the "mdEnpointsAMAPolicyInitiative" and "mdEndpointsAMADeploymentName" variables. [1] [2]
• Added a new block of code to assign the new Microsoft Defender for Endpoints policy initiative to the intermediate root management group if the condition is true.

Addition of a new policy assignment:

• eslzArm/managementGroupTemplates/policyAssignments/DINE-MDEndpointsAMAPolicyAssignment.json: Added a new policy assignment file for the Microsoft Defender for Endpoints policy initiative.

Azure Public

As part of this Pull Request I have

• Checked for duplicate Pull Requests
• Associated it with relevant issues, for tracking and closure.
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Performed testing and provided evidence.
• Ensured contribution guidance is followed.
• Updated relevant and associated documentation.
• Updated the "What's New?" wiki page (located: /docs/wiki/whats-new.md)