Git: Clone destination folder dialog never appears for a repo with no prior clone history

Does this issue occur when all extensions are disabled?: No (occurs with "GitHub Pull Requests" extension enabled; not tested with all extensions disabled)

>
- VS Code Version: Stable, reproduced on 1.115.0, 1.116.0, 1.134.0, and 1.135.0
- OS Version: Windows 11 (10.0.26200)

Steps to Reproduce:

1. Open VS Code with no folder open (File → Close Folder).
2. Open the Command Palette (Ctrl+Shift+P).
3. Type and run Git: Clone.
4. Either paste a repository URL directly, or select "Clone from GitHub" and pick a repo from the list — a repo that has NEVER been cloned locally before (no prior clone history/metadata for it).
5. After selecting/confirming the repo, the flow skips straight to "Would you like to open the repository?" without ever showing the native folder picker.

Expected Behavior

The native OS folder picker should appear so the destination/parent folder can be chosen before cloning.

Actual Behavior

The destination folder selection step is completely skipped. The Git output channel shows no `git clone` command was ever run — only repeated `git rev-parse --show-toplevel` failures (`fatal: not a git repository`). No folder is created on disk.

Additional Information

- This appears related to #307824 / PR #309247, but that fix's title ("always show clone destination picker when cached repo exists") suggests it only covers repos with existing cached clone metadata.
- Repos that DO have prior clone history (previously cloned, then deleted, tried again via "Clone again") correctly show "Open Existing Repository Clone" and, if reselecting via "Clone again", correctly show the folder picker.
- Repos with NO prior history never show the folder picker, regardless of clone method (URL paste or GitHub picker), across all versions tested (1.115–1.135).