`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_

Start by reproducing `copilot -p "test"` with telemetry forced on in managed settings, then compare its telemetry initialization with the IntelliJ CLI-harness chat path. Trace the OTEL setup for both triggers and verify that telemetry is emitted in each scenario when the override is enabled.

Written by the indexing model from the issue text.