Bug description Groq API integration tests in OpenAiCompatibleChatModelIT.java are currently commented out with a comment indicating the API was down on 26.01.2025, but the API is now operational. The tests should be re-enabled to restore full integration test coverage.

Environment - Spring AI version: Current main branch (latest) - Java version: Java 17+ (based on project requirements) - Test framework: JUnit 5 - File location: models/spring-ai-openai/src/test/java/org/springframework/ai/openai/chat/OpenAiCompatibleChatModelIT.java

Steps to reproduce 1. Clone the Spring AI repository 2. Navigate to models/spring-ai-openai/src/test/java/org/springframework/ai/openai/chat/ 3. Open OpenAiCompatibleChatModelIT.java 4. Observe lines 63-68 where Groq API tests are commented out with the comment: // (26.01.2025) Disable 5. because the Groq API is down. TODO: Re-enable when the API is back up. 5. Set GROQ_API_KEY environment variable 6. Run integration tests - Groq tests are skipped due to commented code

Expected behavior When GROQ_API_KEY environment variable is set, Groq API integration tests should run as part of the openAiCompatibleApis() test suite, similar to how OpenRouter and other API tests work.

Minimal Complete Reproducible example

// Current state (problematic code):
// (26.01.2025) Disable because the Groq API is down. TODO: Re-enable when the API
// is back up.
// if (System.getenv("GROQ_API_KEY") != null) {
// builder.add(new OpenAiChatModel(new OpenAiApi("https://api.groq.com/openai",
// System.getenv("GROQ_API_KEY")),
// forModelName("llama3-8b-8192")));
// }

// Expected state (correct code):
if (System.getenv("GROQ_API_KEY") != null) {
    builder.add(new OpenAiChatModel(new OpenAiApi("https://api.groq.com/openai",
        System.getenv("GROQ_API_KEY")),
        forModelName("llama3-8b-8192")));
}