Fix AMQP remote connection close cleanup

[arnabnandy7]

Description

Fixes an azure-core-amqp connection cleanup issue when a remote endpoint closes an AMQP connection with an error condition, such as amqp:connection:forced.

Previously, ConnectionHandler suppressed the error because the remote endpoint was already in the CLOSED state. As a result, ReactorConnection did not receive a terminal signal and could retain connection and transport resources across reconnects.

This change:

• Emits the mapped AmqpException for error-bearing remote connection closes.
• Preserves the existing CLOSED signal for graceful remote closes.
• Adds regression tests for graceful and amqp:connection:forced closes.
• Updates the azure-core-amqp changelog.

Fixes #49440.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

Test validation: ConnectionHandlerTest - 9 tests passed with no failures or errors.

[github-actions]

Thank you for your contribution @arnabnandy7! We will review the pull request and get back to you soon.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
34 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

This pull request fixes an azure-core-amqp cleanup/termination issue when the remote AMQP peer closes the connection with an error condition (for example amqp:connection:forced). The change ensures the ConnectionHandler emits a terminal error signal (mapped to AmqpException) instead of suppressing it when the remote endpoint is already CLOSED, helping avoid retaining connection/transport resources across reconnect cycles.

Changes:

• Emit a mapped terminal error (AmqpException) from onConnectionRemoteClose when the remote close includes an AMQP error condition.
• Preserve existing behavior for graceful remote closes (still emits EndpointState.CLOSED).
• Add regression tests covering both graceful remote close and amqp:connection:forced remote close, and update the changelog.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
sdk/core/azure-core-amqp/src/main/java/com/azure/core/amqp/implementation/handler/ConnectionHandler.java	Ensures remote close events with an error condition surface a terminal error instead of being suppressed.
sdk/core/azure-core-amqp/src/test/java/com/azure/core/amqp/implementation/handler/ConnectionHandlerTest.java	Adds regression tests for remote close signaling behavior (graceful vs error-bearing close).
sdk/core/azure-core-amqp/CHANGELOG.md	Documents the bug fix in the upcoming unreleased version.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.