Display per-response elapsed time during and after generation

## Problem

When Copilot CLI is generating a response, there's no indication of how long it's been running. For short responses this isn't a problem, but for long-running operations (especially in autopilot mode where the agent may work autonomously for minutes at a time), I'd like to know:

- How long has the current response been going?
- How long did the previous response take?

Today, the only signal that "something is happening" is the spinner/animation, which doesn't tell me whether I'm at 5 seconds or 5 minutes.

## Proposed solution

1. **During generation**: display a running elapsed-time counter alongside the spinner.
2. **After completion**: print a short summary line with the total elapsed time for that response.

Example flow:

```
> Refactor the authentication module to use OAuth.

⠋ Working... 0:23
```

Then on completion:
```
✓ Done in 1m 47s.
```

## Why this matters

- **Autopilot mode** especially benefits: when the agent is running unattended for a while, the elapsed counter helps me decide whether to keep waiting or intervene.
- **Performance awareness**: knowing typical response times makes it easy to notice when something is unusually slow (network issue, stuck tool call, etc.).
- **Productivity**: lets me estimate when to context-switch back to a long-running session.

## Reference

Claude Code does this well: during generation it shows a running counter (e.g., `✻ Sautéed for 25s...`), and on completion prints the final elapsed time. Low-visual-noise, useful at a glance.

## Related

#1784 (collapsible real-time session stats panel) covers a broader vision of per-session metrics including duration. This issue is narrower: just the per-response elapsed time, always visible without needing to expand a panel.

Comece localizando os pontos de entrada do spinner e da geração de respostas da CLI e, em seguida, rastreie onde a geração começa e termina. Adicione um contador visível durante a execução e um resumo de conclusão para cada resposta, incluindo o uso de autopilot, e verifique manualmente ambos os estados com respostas de execução curta e longa.

Escrita pelo modelo de indexação a partir do texto da issue.