OTEL `chat` spans do not have the proper parent span for subagents

Describe the bug

When OTEL is enabled and copilot uses the task tool to start a subagent, an invoke_agent span is created which contains all the execute_tool spans, but a single chat span at the very beginning. All other chat spans do not have the appropriate parent set to the invoke_agent span.

This is especially confusing when copilot starts multiple subagents, because then the chat spans are all mixed together, and the github.copilot.turn_id do not make sense.

Affected version

No response

Steps to reproduce the behavior

1. Enable OTEL
2. Ask copilot to use the task tool multiple times, e.g. "Using the task tool, ask three sub-agents to summarize the last five commits of this project, then compare their summaries."
3. Inspect the OTEL trace

Expected behavior

No response

Additional context

No response

Reproduce el trace con OTEL habilitado utilizando varios subagentes de task-tool y, a continuación, inspecciona los spans invoke_agent, execute_tool y chat resultantes. Sigue la ruta de relación padre de los spans y verifica que cada span de chat esté agrupado bajo el span invoke_agent correspondiente y que los valores de github.copilot.turn_id ya no se mezclen entre subagentes.