Skip attach E2E test on in-box Windows PowerShell

CanAttachScriptWithPathMappings hangs on in-box Windows PowerShell 5.1
since the windows-2025-vs2026 runner image refreshed from 20260608 to
20260614. The cross-process Debug-Runspace attach wedges and the test
rides the job timeout; the windows-latest leg cannot complete.

Scope the skip to IsWindowsPowerShell so the in-box WinPS suites
(including CLM) are exempt while PowerShell Core, the preview, macOS, and
Linux keep full coverage of the attach path. This is a stopgap pending a
real fix for the in-box attach deadlock, tracked by #2323; the 30-minute
timeout-minutes backstop in ci-test.yml stays as a guard.

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

Author: andyleejordan

test/PowerShellEditorServices.Test.E2E/DebugAdapterProtocolMessageTests.cs

@@ -635,6 +635,13 @@ public async Task CanLaunchScriptWithNewChildAttachSessionAsJob()
         [SkippableFact(Timeout = 15000)]
         public async Task CanAttachScriptWithPathMappings()
         {
+            // This passes against PowerShell Core but hangs against in-box Windows
+            // PowerShell since the windows-2025-vs2026 runner image moved from
+            // 20260608 to 20260614: the cross-process Debug-Runspace attach wedges
+            // and rides the job timeout. Skipped pending a real fix; see #2323.
+            Skip.If(PsesStdioLanguageServerProcessHost.IsWindowsPowerShell,
+                "Attach wedges on Windows PowerShell since the 20260614 runner image; see #2323.");
+
             Skip.If(PsesStdioLanguageServerProcessHost.RunningInConstrainedLanguageMode,
                 "Breakpoints can't be set in Constrained Language Mode.");