Fix error about test by docker

[rujche]

• Link to related PRs:

  • Add ServiceBus Service Connection for Docker Compose and Testcontainers #44019
  • Add EventHubs Service Connection for Docker Compose and Testcontainers #47926
  • Add docker related unit tests in new projects Azure-Samples/azure-spring-boot-samples#825

• Before current PR, the unit test will fail when some property configured in application.yaml. Here is the screenshot:

  

• After current PR, test passed. Here is the screenshot:

  

[Copilot]

Pull request overview

This pull request fixes test failures that occur when Azure service properties (like accountName, namespace, or endpoint) are configured in application.yaml alongside Docker Testcontainers or Docker Compose connection details beans. The fix ensures that connection strings provided by ConnectionDetails beans are the single source of truth by nulling out properties that would otherwise be used to derive conflicting endpoint URLs or fully qualified domain names.

Changes:

• Nulls properties that derive connection information (accountName, namespace, endpoint) when ConnectionDetails beans provide connection strings
• Ensures consistency across Storage Blob, Storage Queue, Service Bus, and Event Hubs configurations

Reviewed changes

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

File	Description
ConfigurationWithConnectionDetailsBean.java (Storage Queue)	Sets accountName to null after setting connection string and endpoint from connection details
ConfigurationWithConnectionDetailsBean.java (Storage Blob)	Sets accountName and endpoint to null after setting connection string from connection details
ConfigurationWithConnectionDetailsBean.java (Service Bus)	Sets namespace to null after setting connection string from connection details
ConfigurationWithConnectionDetailsBean.java (Event Hubs)	Sets namespace to null after setting connection string from connection details

[rujche]

/azp run java - spring - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).