Issues auto-updating CLI

### Describe the bug

It took 3 sessions to get the latest version of the CLI.

### Affected version

1.0.11 and 1.0.14

### Steps to reproduce the behavior

- I just started a new Copilot CLI terminal in VS Code Insiders (opened an integrated terminal, typed `copilot` myself, then asked one question), and I got an updating error after the CLI responded to my question. I'm using `v1.0.11` of the CLI.

> Error auto updating: Failed to download package: Error: ENOENT: no such file or directory, rename 'C:\Users\brmurtau.copilot\pkg\universal\1.0.14-0' -> 'C:\Users\brmurtau.copilot\pkg\universal.replaced-1.0.14-0-34924-1774894188189'

- I tried completely killing the terminal, opening a new one, and typing `copilot` and the same prompt again, and now I don't get the auto updating error message, but I do see there's a new version of the CLI (v1.0.14-0) that I wasn't auto-updated to
- If I kill the terminal again and then complete the same steps a third time, now I'm updated to `v1.0.14-0`

### Expected behavior

Auto-updating works correctly the first time I open a new terminal.

### Additional context

_No response_

Start at the `copilot` CLI entry point and reproduce the update from v1.0.11 to v1.0.14-0 in a Windows integrated terminal. Trace the package download and rename operation shown in the ENOENT error; done means the first new terminal updates successfully without the error and runs v1.0.14-0.

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