FEAT: Add GroqChatTarget (#704)

[jsdlm]

Description

Adds GroqChatTarget, a new chat target for interacting with Groq’s OpenAI-compatible API.

• The existing OpenAIChatTarget does not work with Groq because Groq expects messages.0.content to be a string, while OpenAI/Azure accept a list of dictionaries.
• This PR also adds unit tests for GroqChatTarget and documentation.

---

Changes

• Added GroqChatTarget (pyrit/prompt_target/groq_chat_target.py)
  • Inherits from OpenAIChatTarget
  • Overrides _complete_chat_async to ensure content is formatted correctly for Groq
  • Overrides _initialize_non_azure_vars to set up Groq-specific API parameters
  • Uses GROQ_API_KEY and GROQ_MODEL_NAME environment variables
• Added unit tests (tests/unit/target/test_groq_chat_target.py) adapted from OpenAIChatTarget tests
• Added documentation (doc/code/targets/groq_chat_target.py)

---

Related Issue

#704

[jsdlm]

@jsdlm please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree

[romanlutz]

Sure, this solution is acceptable for me. We'd need unit tests, though. Can you essentially replicate the openai ones with modifications?

[jsdlm]

Thanks! I've now added unit tests as well.

In the class, I refined the implementation to make it fully compatible with Groq’s API. This includes enforcing the correct API base URL (https://api.groq.com/openai/v1/), updating the environment variables to GROQ_API_KEY and GROQ_MODEL_NAME, and adapting _initialize_non_azure_vars to align with Groq’s authentication and request structure.

For the unit tests, I followed the OpenAI ones as a base, adapting them to match the new Groq implementation.

[jsdlm]

[rlundeen2]

Approving! I'll likely combine this target along with my PR. Thanks for doing this, as it'll help our targets be more generic

[jsdlm]

Thanks for the review and for merging! Appreciate the collaboration.