`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 内容生成。