[BUG] Keep default options consistent between Spring and Java SDK

[yiliuTo]

Context

In Spring configuration properties, it's common that there is explicit default-value assignment, e.g., the load-balancing strategy. However, this can cause the default values of Spring and Java SDK become inconsistent when SDK changed their default options. Referring to #25039

Solution

Remove those default options in Spring properties and hand over to SDK.

[yiliuTo]

All the auto-configuration components provided by Spring Cloud Azure can be devided into 3 types: auto-configuration for Azure services with Azure SDK, auto-configuration without Azure SDK and other internal modules. This issue aims to keep the consistency of the default values between auto-configuration modules with Azure SDK and Azure SDK.

Auto-configuration with Azure SDK

Service	Needs aligned	Property with default values	Breaking changes
App Config	❎	NA	NA
Cosmos & Data cosmos	✅	connection-mode	No
Service Bus	✅	receive-mode auto-complete sub-queue max-auto-lock-renew-duration maxConcurrentCalls	No
Event Hubs	✅	load-balancing.strategy	changed from BALANCED to GREEDY
KV Cert	❎	NA	NA
KV Secret	❎	NA	NA
Storage Blob	❎	NA	NA
Storage File Share	❎	NA	NA
Storage Queue	❎	NA	NA
Resource Manager	❎	NA	NA
Global - credential	❎	NA	NA
Global - retry	✅	retry.mode	NA
Global - proxy	❎	NA	NA
Global - client	✅	transport-type	No
Global - profile	❎	NA	NA

Note, the default value of the profile property cloud-type cannot be removed, which is required here.

Auto-configuration without Azure SDK

• ✖️ aad & b2c --> omit
• ✖️ jdbc --> covered by global properties
• ✖️ event hubs for kafka --> covered by global properties
• ✖️ service bus for jms --> omit
• ✖️ redis -> covered by resource manager
• ✖️ cloud foundry --> omit

Internal modules

• ✖️ compatibility --> omit