`copilot -p` does not emit OTEL telemetry even with server-managed settings overrides

### Describe the bug

Running copilot cli with -p doesn't emit telemetry with server-managed settings:

```
{
"telemetry": {
"enabled": true,
...
}
}
```

This could also contribute to sessions running under the CLI in the chat window do not show telemetry in IntelliJ:

We need both of these scenarios covered with telemetry.

### Affected version

1.0.71

### Steps to reproduce the behavior

copilot -p "test"

or in IntelliJ select CLI as the harness and use the chat normally

### Expected behavior

OTEL telemetry gets emitted no matter how copilot is triggered when OTEL is forced on in managed settings.

### Additional context

_No response_

首先，在受管理設定中強制開啟 telemetry 的情況下重現 `copilot -p "test"`，然後將其 telemetry 初始化與 IntelliJ CLI-harness 的聊天路徑進行比較。追蹤兩個觸發器的 OTEL 設定，並驗證在啟用 override 時每種情境都會發出 telemetry。

由索引模型根據 Issue 內容生成。