Update changelog for ArcResourceBridge and Automanage

[lijinpei2008]

Description

#28179
#28181

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.

[github-actions]

To the author of the pull request,
This PR was labeled "Contains Breaking Change" because breaking changes have been detected by the static analysis pipeline.

• According to our policy, breaking changes can only take place during major release and they must be preannounced.
• Please follow our guide on the detailed steps.
• Required: Please fill in the task below to facilitate our contact,you will receive notifications related to breaking changes.

[Copilot]

Pull Request Overview

This PR updates changelog entries for two Azure PowerShell modules (Automanage and ArcResourceBridge) to provide clearer, more user-focused release notes. The changes replace technical implementation details about code generator upgrades with a user-centric message about experience improvements and breaking changes.

Key Changes:

• Replaced technical changelog entries with user-facing descriptions
• Updated link references from internal documentation to external Microsoft documentation
• Clarified that breaking changes may be introduced

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/Automanage/Automanage/ChangeLog.md	Updated "Upcoming Release" entry to describe user-facing improvements and breaking changes instead of technical code generator details
src/ArcResourceBridge/ArcResourceBridge/ChangeLog.md	Updated "Upcoming Release" entry with same user-focused messaging as Automanage module

[Copilot]

The changelog entry should explain what specifically changed from the user's perspective. 'Improved user experience and consistency' is too vague. Consider describing the actual changes users will experience (e.g., renamed cmdlets, changed parameters, new functionality). Additionally, the phrase 'refer to [here]' has awkward phrasing - consider 'refer to [this guide]' or 'see [documentation]'.

[Copilot]

The changelog entry should explain what specifically changed from the user's perspective. 'Improved user experience and consistency' is too vague. Consider describing the actual changes users will experience (e.g., renamed cmdlets, changed parameters, new functionality). Additionally, the phrase 'refer to [here]' has awkward phrasing - consider 'refer to [this guide]' or 'see [documentation]'.