Responses API: AssistantReasoningDeltaEvent and AssistantReasoningEvent triggered with empty content via BYOK providers

When using GitHub Copilot SDK in a BYOK (Bring Your Own Key) setup—whether the provider is OpenAI or vLLM—the Responses API triggers both AssistantReasoningDeltaEvent and AssistantReasoningEvent, but the content (reasoning or explanation) for these events is always empty.

**Steps to reproduce:**
1. Set up Copilot SDK to use BYOK with OpenAI or vLLM as the provider (Windows or WSL). Example .NET code configuration:

```csharp
await using var session = await client.CreateSessionAsync(new SessionConfig
{
Provider = new ProviderConfig
{
Type = "openai",
BaseUrl = "https://api.openai.com/v1",
ApiKey = "your_api_key",
WireApi = "responses",
},
ReasoningEffort = "high",
Model = "gpt-5.4-2026-03-05",
OnPermissionRequest = PermissionHandler.ApproveAll,
Streaming = true
});
```

2. Trigger chat completions or requests that should provide reasoning content through the Responses API.
3. Observe that AssistantReasoningDeltaEvent and AssistantReasoningEvent are triggered, but the content is always empty.

**Expected behavior:**
These events should include the reasoning/explanation content returned by the provider's API. Content should not be empty if the provider returns a reasoning field.

**Context:**
- Environment: Windows, WSL
- Copilot SDK version: 0.3.0
- BYOK provider: OpenAI or vLLM

Start by tracing the Responses API handling for AssistantReasoningDeltaEvent and AssistantReasoningEvent, then reproduce the issue using the shown BYOK configuration with OpenAI or vLLM. Compare the provider's reasoning field with the event payload; done when non-empty reasoning is propagated into both events when the provider returns it.

Scritto dal modello di indicizzazione a partire dal testo della issue.