Spring-ai Merge seperate AutoConfiguration classes that produce both a ChatClient and EmbeddingClient that share a common connection bean definition

These are the ones that need to change

• BedrockTitanChatAutoConfiguration and BedrockTitanEmbeddingAutoConfiguration share a TitanEmbeddingBedrockApi bean definition.
• HuggingfaceAutoConfiguration should be renamed HuggingfaceChatAutoConfiguration as it only contains autoconfiguration for the ChatClient
• OllamaChatAutoConfiguration and OllamaEmbeddingAutoConfiguration should be merged into OllamaAutoConfiguration as they share a OllamaApi bean definition.

Comment From: markpollack

Upon deeper review, BedrockTitanChatAutoConfiguration and BedrockTitanEmbeddingAutoConfiguration use underlying connectivity classes, TitanChatBedrockApi and TitanEmbeddingBedrockApi so they need to remain separate. The bean name for these connectivity classes was the same, this should be changed for clarity.

The merge should happen for the case of Ollama.

The HuggingfaceAutoConfiguration was renamed HuggingfaceChatAutoConfiguration