Unable to find my previous copilot CLI sessions consistently.

### Describe the bug

The one and very big frustration that I have with copilot CLI recently is not being able to resume my session that I just worked in the previous day.

For some reason when I use the `/resume`, `--resume` flag it shows many sessions but not all, the ones that I just worked yesterday don't show up.

I have to know ahead of time where was the cwd from that session (which is almost impossible given the new worktree feature, generating random branch / directory names, which normally is the cwd for the session.

Please allow the /resume local session having a `global local` option I don't have to care where that session started or what was last CWD.

### Affected version

v1.0.65

### Steps to reproduce the behavior

1. Start a session in a folder A
2. Generate the worktree (folder B)
3. Move the CWD to the new worktree (folder A -> folder B)
4. Do stuff.
5. Close copilot
6. Open copilot in folder A
7. Try to resume the session, it may not list there.

---

Check your .copilot\session-state\session-ids (order by the most recent created)

1. Open copilot in any folder
2. Open resume option
3. The local sessions list doesn't reflect the actual local sessions in the `.copilot` folder

### Expected behavior

copilot\session-state\session-ids should transparently be reflected by the /resume (local sessions)

### Additional context

_No response_

まず、記載されているフォルダーと worktree の手順を再現し、その後 `.copilot/session-state/session-ids` を調べ、そこに最近作成されたセッションと `/resume` のローカルセッション一覧を比較します。元のフォルダーから Copilot を開いたときに、そこに保存されているセッションが透過的に反映されれば完了です。

索引モデルが issue の本文から書いたものです。