[FEATURE REQ] Change sender's default JmsConnectionFactory from ServiceBusJmsConnectionFactory to CachingConnectionFactory

[rujche]

Current behavior

	Property (spring.jms.servicebus.pool.enabled and spring.jms.cache.enabled) not set or set to false	Property (spring.jms.servicebus.pool.enabled or spring.jms.cache.enabled) set to true
sender side	ServiceBusJmsConnectionFactory	CachingConnectionFactory or JmsPoolConnectionFactory
receiver side	ServiceBusJmsConnectionFactory	CachingConnectionFactory or JmsPoolConnectionFactory

Expected behavior

Comment from @vinaysurya

If we don't use a CachingConnectionFactory on Sender side, I'm afraid when using JMSTemplate every send from Spring SDK will create and close a connection which will be very inefficient.

	Property (spring.jms.servicebus.pool.enabled and spring.jms.cache.enabled) not set or set to false	Property (spring.jms.servicebus.pool.enabled or spring.jms.cache.enabled) set to true
sender side	CachingConnectionFactory	CachingConnectionFactory or JmsPoolConnectionFactory
receiver side	ServiceBusJmsConnectionFactory	CachingConnectionFactory or JmsPoolConnectionFactory

Relate codes

1. azure-sdk-for-java/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java

   Lines 29 to 48 in d9d47b6

   	JmsListenerContainerFactory<?> jmsListenerContainerFactory(
   	DefaultJmsListenerContainerFactoryConfigurer configurer, ConnectionFactory connectionFactory) {
   	DefaultJmsListenerContainerFactory jmsListenerContainerFactory = new DefaultJmsListenerContainerFactory();
   	configurer.configure(jmsListenerContainerFactory, connectionFactory);
   	jmsListenerContainerFactory.setPubSubDomain(Boolean.FALSE);
   	configureCommonListenerContainerFactory(jmsListenerContainerFactory);
   	return jmsListenerContainerFactory;
   	}
   	@Bean
   	@ConditionalOnMissingBean(name = "topicJmsListenerContainerFactory")
   	JmsListenerContainerFactory<?> topicJmsListenerContainerFactory(
   	DefaultJmsListenerContainerFactoryConfigurer configurer, ConnectionFactory connectionFactory) {
   	DefaultJmsListenerContainerFactory jmsListenerContainerFactory = new DefaultJmsListenerContainerFactory();
   	configurer.configure(jmsListenerContainerFactory, connectionFactory);
   	jmsListenerContainerFactory.setPubSubDomain(Boolean.TRUE);
   	configureCommonListenerContainerFactory(jmsListenerContainerFactory);
   	configureTopicListenerContainerFactory(jmsListenerContainerFactory);
   	return jmsListenerContainerFactory;
   	}

2. azure-sdk-for-java/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsConnectionFactoryConfiguration.java

   Lines 59 to 72 in 1ab5874

   	public void registerBeanDefinitions(AnnotationMetadata importingClassMetadata,
   	BeanDefinitionRegistry registry) {
   	BindResult<Boolean> poolEnabledResult = Binder.get(environment).bind("spring.jms.servicebus.pool.enabled", Boolean.class);
   	BindResult<Boolean> cacheEnabledResult = Binder.get(environment).bind("spring.jms.cache.enabled", Boolean.class);
   	if (isPoolConnectionFactoryClassPresent() && poolEnabledResult.orElseGet(() -> false)) {
   	registerJmsPoolConnectionFactory(registry);
   	return;
   	}
   	if (isCacheConnectionFactoryClassPresent() && cacheEnabledResult.orElseGet(() -> false)) {
   	registerJmsCachingConnectionFactory(registry);
   	return;
   	}

[rujche]

Current status

1. From azure-spring-boot-samples, the sender is JmsTemplate bean.
2. The sender side, related code is in spring-boot/../JmsClientConfigurations.java, the JmsTemplate bean will only be configured when there is only one bean with type ConnectionFactory. @ConditionalOnSingleCandidate(ConnectionFactory.class).
3. The receiver side, related code is in azure-sdk-for-java/.../ServiceBusJmsContainerConfiguration, it also uses the bean ConnectionFactory, it's the same one used in spring-boot/../JmsClientConfigurations.java

Implementation suggestion

1. Keep the configuration with only one bean with type ConnectionFactory, to make the spring-boot/../JmsClientConfigurations.java can still work.
2. On the sender side, in azure-sdk-for-java/.../ServiceBusJmsConnectionFactoryConfiguration, the ConnectionFactory's type should satisfy the sender's requirement written in current issue description: Use CachingConnectionFactory by default.
3. On the receiver side, the azure-sdk-for-java/.../ServiceBusJmsContainerConfiguration won't use bean ConnectionFactory, it uses a newly created ConnectionFactory (not a bean) that is just used for its own. One problem: It cannot be overridden if a customer registers a bean with type ConnectionFactory. It may not be a problem, because the current implementation doesn't allow customers to customize by registering a bean with type ConnectionFactory.