Document why clearTerminal can't restore prior focus

The focus-restore is best-effort: `workbench.action.terminal.clear` always
focuses the terminal, and VS Code's stable API exposes no way to learn what
was focused before the clear (`TerminalState` has no focus flag, and
`activeTextEditor` does not go `undefined` when the terminal is focused). So
we can't perfectly return focus to wherever it was.

Spell out the resulting caveat in a comment: running `Clear-Host` directly in
the console while `focusConsoleOnExecute` is `false` will also move focus to
the editor. That edge case is consistent with the user's stated preference to
keep focus in the editor, and fixing it properly isn't possible without a
focus-state signal the API doesn't provide.

Drafted by Copilot (Claude Opus 4.8).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: andyleejordan

src/features/ExtensionCommands.ts

@@ -338,8 +338,13 @@ export class ExtensionCommandsFeature extends LanguageClientConsumer {
 
         await vscode.commands.executeCommand("workbench.action.terminal.clear");
 
-        // Clearing the terminal focuses it, but if the user has asked us not to
-        // focus the console on execute, then we restore focus to the editor.
+        // Clearing the terminal also focuses it, and VS Code exposes no way to
+        // learn what was focused beforehand (there's no terminal focus state,
+        // and `activeTextEditor` doesn't go undefined when the terminal is
+        // focused). So when the user has opted out of focusing the console on
+        // execute, we best-effort restore focus to the editor. The caveat is
+        // that running `Clear-Host` directly in the console also moves focus to
+        // the editor under this setting.
         const focusConsoleOnExecute = vscode.workspace
             .getConfiguration("powershell.integratedConsole")
             .get<boolean>("focusConsoleOnExecute", true);