fix: use powershell.exe instead of pwsh.exe for build_data_writer (bazel-contrib#3553)

Stock Windows ships with Windows PowerShell 5.1 (powershell.exe) but not
PowerShell 7+ (pwsh.exe). Using pwsh.exe causes builds to fail on
machines without PowerShell 7 installed. Also adds -ExecutionPolicy
Bypass since Windows PowerShell defaults to Restricted policy which
blocks .ps1 script execution.

Fixes bazel-contrib#3552

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Richard Levasseur <richardlev@gmail.com>

Author: 5 people

python/private/py_executable.bzl

@@ -1369,9 +1369,17 @@ def _write_build_data(ctx):
     action_args = ctx.actions.args()
     writer_file = ctx.files._build_data_writer[0]
     if writer_file.path.endswith(".ps1"):
-        action_exe = "pwsh.exe"
-        action_args.add("-File")
-        action_args.add(writer_file)
+        # powershell.exe is used for broader compatibility
+        # It is installed by default on most Windows versions
+        action_exe = "powershell.exe"
+        action_args.add_all([
+            # Bypass execution policy is needed because,
+            # by default, Windows blocks ps1 scripts.
+            "-ExecutionPolicy",
+            "Bypass",
+            "-File",
+            writer_file,
+        ])
         inputs.add(writer_file)
     else:
         action_exe = ctx.attr._build_data_writer[DefaultInfo].files_to_run