Simplify change log for batch

[dolauli]

Description

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[Copilot]

Pull Request Overview

This PR simplifies the Batch module's changelog for the upcoming release by consolidating detailed breaking change entries into a single API version upgrade note. The detailed changes (removal of commands, parameters, and properties, plus addition of new features) have been replaced with a concise statement about upgrading from API version 2022-10-01 to 2024-07-01.

• Removed 26 lines of detailed breaking change documentation
• Added 1 line noting the API version upgrade

[Copilot]

The changelog entry lacks detail about what changes users should expect from this API upgrade. According to the coding guidelines for ChangeLog.md files (CodingGuidelineID: 1000002), entries should be written from the user's perspective and explain what changed and how it affects their usage. The removed content documented significant breaking changes including removal of commands (Get-AzBatchRemoteDesktopProtocolFile, certificate-related commands), removal of parameters (CloudServiceConfiguration, CertificateReferences, etc.), and new features (new enum values, new properties). Users upgrading will need this information to understand the impact. Consider either: (1) restoring the detailed changelog entries, or (2) adding a reference to the migration guide at https://go.microsoft.com/fwlink/?linkid=2333229 mentioned in version 3.7.1, such as: '* Upgraded API version from 2022-10-01 to 2024-07-01. For details on breaking changes, please refer to https://go.microsoft.com/fwlink/?linkid=2333229'