Use dedicated JMS listener connection factory

[arnabnandy7]

Description

Fixes the Service Bus JMS connection factory configuration so applications can use:

• JmsPoolConnectionFactory for sending messages.
• ServiceBusJmsConnectionFactory for listener containers.

This combination is selected by configuring:

spring.jms.servicebus.pool.enabled=true
spring.jms.cache.enabled=false

Previously, this property combination caused both the sender and listener containers to use JmsPoolConnectionFactory. This prevented Standard-tier Service Bus topic subscriptions from using the native ServiceBusJmsConnectionFactory.
The listener connection factory decision table now selects a dedicated ServiceBusJmsConnectionFactory for this combination, while the sender continues to use JmsPoolConnectionFactory.

The change includes tests for both Standard and Premium Service Bus tiers. The tests verify that queue and topic listener containers share the dedicated native connection factory and do not use the pooled sender connection factory.
The corresponding connection factory tables in the CHANGELOG have also been updated.

Fixes: #49308

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.

[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 3 pipeline(s).
32 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 PR fixes the Service Bus JMS auto-configuration so that when spring.jms.servicebus.pool.enabled=true and spring.jms.cache.enabled=false, the sender continues to use JmsPoolConnectionFactory while listener containers use a dedicated native ServiceBusJmsConnectionFactory (enabling Standard-tier topic subscriptions).

Changes:

• Updated the listener-container connection factory decision table to select ServiceBusJmsConnectionFactory for pool=true + cache=false.
• Added an auto-configuration test covering the pool=true + cache=false case across Standard and Premium tiers.
• Updated the Spring module CHANGELOG connection-factory tables to reflect the corrected behavior.

Reviewed changes

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

File	Description
sdk/spring/spring-cloud-azure-autoconfigure/src/test/java/com/azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsAutoConfigurationTests.java	Adds a new parameterized test verifying listener containers use a native/dedicated connection factory when pooling is enabled and caching is disabled.
sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java	Adjusts the listener container decision table so pool=true + cache=false yields ServiceBusJmsConnectionFactory.
sdk/spring/CHANGELOG.md	Updates the documented decision tables to match the new listener container behavior.

[Copilot]

Pull request overview

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

[Copilot]

Pull request overview

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