Giskard LLM-as-a-judge fails on Azure OpenAI: Must provide an engine or deployment_id

# Giskard LLM-as-a-judge fails on Azure OpenAI: Must provide an engine or deployment_id

## What's going on

Running a Giskard LLM-as-a-judge test on an Azure OpenAI model fails with `Must provide an 'engine' or 'deployment_id' parameter to create a class 'openai.api_resources.chat_completion.ChatCompletion'`, even though `deployment_name` is set on `AzureChatOpenAI`. The user's own QA chain runs fine; only the Giskard test execution fails.

## The verified fix

Cause: Giskard's scan evaluates generated answers through its own internal OpenAI client, which read your `OPENAI_*` environment variables and ignored your Azure config, hence the missing engine/deployment_id. The fix was Azure support for the scan: set `AZURE_OPENAI_API_KEY`, `AZURE_OPENAI_ENDPOINT`, `OPENAI_API_VERSION`, and `GISKARD_SCAN_LLM_MODEL` (see the maintainer's PR linked on the issue). Note the judge still needs a function-calling-capable model, so GPT-4 is recommended.

Source: https://github.com/Giskard-AI/giskard-oss/issues/1614

## How to use this

Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.