feat: Add OAI_RESPONSES model provider and implement Responses API client tests

- Updated ModelProfile to include OAI_RESPONSES in the ModelProvider enum.
- Created CompletionClientTest to validate text and chat completion functionalities.
- Added ResponsesApiClientTest to test Responses API interactions, including model listing and conversation handling.
- Implemented ResponsesApiDialectTestConfiguration for managing reasoning efforts in tests.
- Updated application-test.properties to include a new profile for responses.
- Added local-responses.properties configuration for the Responses API.

src/test/resources/application-test.properties

@@ -6,6 +6,7 @@ profile.model.cold=local-chatcompletion
 
 profile.model.textcompletion=local-completion
 profile.model.chatcompletion=local-chatcompletion
+profile.model.responses=local-responses
 profile.model.ollama=local-ollama-chatcompletion
 profile.model.openrouter=local-openrouter-chatcompletion
 #profile.model.azure=llama3.3-70b-azure

src/test/resources/local-responses.properties

@@ -0,0 +1,16 @@
+category=RESPONSES
+prompts=
+tokenizer=llamaServer
+tokenEncoding=cl100k_base
+maxTokens=2500
+maxContextLength=16000
+temperature=0.4
+topP=1.0
+modelProvider=OAI_RESPONSES
+modelName=
+url=http://localhost:5001
+apiKey=
+cost1MInTokens=0
+cost1MCachedInTokens=0
+cost1MOutTokens=0
+cost1MReasoningOutTokens=0