test(e2e): defeat template-filter pollution in the bundle_init wizard (#2123)

## Why

`bundle_init :: should initialize new project` still flakes on the
Windows shard with **"Can't complete cli bundle init wizard"** (its two
follow-on tests then cascade), despite #2034 gating the first keystroke
on tab readiness. Two races remain:

1. **Keystroke focus race** — the editor tab becoming *active* doesn't
guarantee the xterm holds keyboard focus, so keys fired next can land in
the tab chrome instead of the wizard.
2. **Template-filter pollution** — per
`BundleInitWizard.bundleInitInTerminal` (see its own comment), the
Python extension can inject env-setup text into the freshly opened
terminal, and that text lands in the wizard's template **search
filter**. The typed `default-python` then appends to that text, matches
no template, and the wizard stalls until the 40s completion loop times
out.

The terminal buffer isn't reliably readable via the wdio API on this
editor-hosted terminal, so the fix hardens the input path rather than
reading state back.

## What

- **Focus the terminal input** (`workbench.action.terminal.focus`) after
the tab is active and before typing, so wizard keystrokes aren't
swallowed by the editor-tab chrome.
- **Clear the template search filter** with a burst of `Backspace` keys
before typing the template name — a no-op when the filter is already
empty, and it removes any injected env-setup text so `default-python`
matches.
- The Enter-hammering completion loop (which accepts the remaining
default-python prompt defaults) and the ground-truth workspace-root gate
are **unchanged**.

Test-only: no production code, settings, persisted state, telemetry, or
when-clause flags. Nothing changes for shards that never hit the races.

## Verification

- `tsc -p src/test/e2e/tsconfig.json`: **no new errors** (the sole error
is the pre-existing `assert {type: "json"}` in `wdio.conf.ts`, untouched
here).
- `eslint` + `prettier -c`: clean on the touched file.
- e2e-only behavior is verified via **isolated CI runs of
`bundle_init`** on this branch (repeated, since one green run ≠ stable).

This pull request and its description were written by Isaac.

Author: rugpanov

packages/databricks-vscode/src/test/e2e/bundle_init.e2e.ts

@@ -77,12 +77,17 @@ describe("Bundle Init", async function () {
         assert(initTab, "Can't find a tab for project-init terminal wizard");
         await initTab.select();
 
-        // The init wizard runs inside an editor-hosted terminal. Keystrokes sent
-        // before the terminal prompt is ready land in the wrong place and desync
-        // the wizard ("Can't complete cli bundle init wizard") on the slow
-        // Windows shard. The terminal buffer text isn't reliably readable via the
-        // wdio API, but the active-tab title is — gate on the init tab being
-        // active before typing, then use longer settle waits between keystrokes.
+        // The init wizard runs inside an editor-hosted terminal. Two Windows
+        // races desync it into "Can't complete cli bundle init wizard": (1)
+        // keystrokes fired before the tab is active — or before the xterm holds
+        // keyboard focus — land in the wrong place, and (2) the Python extension
+        // can inject env-setup text into the freshly opened terminal that lands
+        // in the template *search filter* (see
+        // BundleInitWizard.bundleInitInTerminal), so a typed "default-python"
+        // appends to that text, matches no template, and the wizard stalls. The
+        // terminal buffer isn't reliably readable via the wdio API, but the
+        // active-tab title is — gate on the init tab being active, move focus
+        // into the terminal, then clear the filter before typing.
         await browser.waitUntil(
             async () => {
                 const activeTab = await editorView.getActiveTab();
@@ -96,6 +101,24 @@ describe("Bundle Init", async function () {
         );
         await sleep(3000);
 
+        // Move keyboard focus into the editor-hosted terminal's input so the
+        // wizard keystrokes below aren't swallowed by the editor-tab chrome.
+        // Return the command so executeWorkbench awaits focus completing.
+        await browser.executeWorkbench((vscode) => {
+            return vscode.commands.executeCommand(
+                "workbench.action.terminal.focus"
+            );
+        });
+        await sleep(1000);
+
+        // Clear the filter before typing (see above); a no-op when it's empty.
+        // Over-provision the backspaces so even a long injected activation line
+        // (a Windows venv/conda activate command with an absolute path) is
+        // fully removed rather than leaving a prefix the template name appends
+        // to.
+        await browser.keys(new Array(200).fill(Key.Backspace));
+        await sleep(1000);
+
         //select temaplate type
         await browser.keys("default-python".split(""));
         await sleep(3000);