Log inputs and outputs of shell activities

### Describe the feature or problem you'd like to solve

I see that copilot cli already logs tool execution events witin the session state folder, but the input and output contents are not populated

### Proposed solution

I believe it will benefit copilot cli and its users to trace what happened. When copilot makes parallel calls the complexity increases exponentially and without structured logging, it makes it difficult to verify corrected or diagnose when or where failures occur

### Example prompts or workflows

1. "I want to replay just the shell commands Copilot ran"
2. "Copilot used the wrong file/path... When did that happen?"
3. "Why is my file broken after I had copilot refactor it?{

### Additional context

_No response_

Start by tracing the existing tool execution event logging in the session state folder, focusing on how shell activity events are recorded. The work is done when shell command inputs and outputs are populated in structured logs, supporting replay and diagnosis of parallel shell calls.

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