bug: /restart fails in sessions created with -w

Describe the bug

A Copilot CLI session started with copilot -w cannot recover after running /restart inside the session. The restart attempts to use both the worktree option and the existing session ID, which results in an option conflict.

Affected version

1.0.80

Steps to reproduce the behavior

1. From any Git repository, start Copilot CLI with an automatically created worktree:

   $ copilot -w
   Created worktree at /path/to/repo.worktrees/<generated-name> (branch <generated-name>)
   

2. Inside the session, run /restart.

3. Observe the error:

   error: option '-w, --worktree[=name]' cannot be used with option '--session-id <id>'
   

Expected behavior

/restart should restart or resume the current session successfully while retaining the existing worktree, without passing -w in conflict with --session-id.

Additional context

• Operating system: macOS
• Shell: zsh
• The session was started with the bare -w option, allowing Copilot CLI to generate the worktree name.

从 /restart 的处理以及使用 copilot -w 启动的会话的命令构造入手。按照 issue 中的三个步骤重现冲突，并检查 -w 和 --session-id 是如何组合的。当 /restart 能够恢复当前会话，同时保留生成的 worktree 且不再发生选项冲突时，即视为完成。