Bug with BYOK: reasoning effort not supported for model "glm-5.2:cloud"

### Describe the bug

I am experiencing an issue when using a custom BYOK configuration with Copilot CLI. Specifically, when I try to use the `--reasoning-effort max` flag, the CLI returns an error stating that the model does not support it, even though the configuration is otherwise valid.

### Affected version

v1.0.68

### Steps to reproduce the behavior

1. Run the following command:

COPILOT_PROVIDER_TYPE=openai COPILOT_PROVIDER_WIRE_API=responses COPILOT_PROVIDER_BASE_URL=https://ollama.com/v1 COPILOT_PROVIDER_API_KEY=$OLLAMA_API_KEY COPILOT_MODEL=glm-5.2:cloud COPILOT_PROVIDER_MAX_PROMPT_TOKENS=999424 COPILOT_PROVIDER_MAX_OUTPUT_TOKENS=131072 copilot --yolo --reasoning-effort max -p hi

2. Observe the error:
Error: Model "glm-5.2:cloud" does not support reasoning effort configuration (requested: "max").

### Expected behavior

The CLI should handle the reasoning effort flag gracefully or allow it for models that might support it, or at least provide a clearer error message indicating why it's not supported for this specific model configuration. Ideally, it should work as expected if the underlying API supports it.

### Additional context

I am confident I can use the command `COPILOT_PROVIDER_TYPE=openai COPILOT_PROVIDER_WIRE_API=responses COPILOT_PROVIDER_BASE_URL=https://ollama.com/v1 COPILOT_PROVIDER_API_KEY=$OLLAMA_API_KEY COPILOT_MODEL=glm-5.2:cloud COPILOT_PROVIDER_MAX_PROMPT_TOKENS=999424 COPILOT_PROVIDER_MAX_OUTPUT_TOKENS=131072 copilot --yolo --reasoning-effort max` without `-p` flag.

This issue only exists when using the `-p` flag.

Commencez par exécuter la commande signalée avec et sans l’option -p, en utilisant les variables d’environnement BYOK indiquées, et comparez la manière dont la validation de l’effort de raisonnement est atteinte. Examinez le chemin d’entrée CLI pour -p ainsi que la vérification des capacités du modèle. Le travail est terminé lorsque la configuration est traitée de manière cohérente, ou lorsque l’erreur de modèle non pris en charge explique clairement la limitation.

Rédigé par le modèle d'indexation à partir du texte de l'issue.