Prepare for June 2025 Core release - Update CHANGELOGs

[Copilot]

This PR prepares the Azure SDK for JS core packages for the June 2025 release (release date: 2025-05-29) by updating CHANGELOGs for packages with functional changes since their last release.

Changes Made

After analyzing all packages in the sdk/core directory, I identified 2 packages that have functional changes requiring a release:

@azure/abort-controller v2.1.3

• Bug Fix: Fixed compiler error in AbortError example snippet PR #31649
• Enhancement: Added React-Native support at top level PR #30521
• Build Improvement: Stop packing d.ts.map files PR #32490

@azure/core-amqp v4.3.7

• Enhancement: Added util polyfill to support browser compatibility PR #33771

Packages Checked (No Release Needed)

The following core packages were analyzed and found to have no functional changes since their last release:

• core-auth, core-client, core-client-rest, core-http-compat, core-lro, core-paging, core-rest-pipeline, core-sse, core-tracing, core-util, core-xml, logger, ts-http-runtime

Process Followed

1. ✅ Fetched all repository tags and prepared environment
2. ✅ For each core package, checked for commits since last release tag using:

   git log "<package-name>_<last-version>..HEAD" -- <package-dir>/src <package-dir>/package.json

3. ✅ Analyzed commits to identify functional vs. non-functional changes
4. ✅ Updated CHANGELOG.md files with proper entries and PR links
5. ✅ Set release date to 2025-05-29 for packages requiring release
6. ✅ Removed empty section headers from CHANGELOGs

Fixes #34529.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[timovv]

This was the correct process. Create a Markdown file at the root of the repository, prepare-changelog.md, detailing the steps that we followed today such that if an AI agent were to be presented with those steps in a GitHub issue in future, it would follow them precisely. The Markdown file should have a "parameters" section at the top which can be edited to change the service directory and the release date.

[Copilot]

This was the correct process. Create a Markdown file at the root of the repository, prepare-changelog.md, detailing the steps that we followed today such that if an AI agent were to be presented wit...

Created prepare-changelog.md at repository root documenting the CHANGELOG preparation process. The file includes an editable parameters section and detailed steps that can be followed precisely for future releases. Commit: cfddff4

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

[timovv]

You must also make an unshallow fetch: git fetch --unshallow || true (it's ok if this command fails)