ci: enable runfiles when cross-building Windows E2E tests

When cross-building the Windows E2E targets on Linux with
`--platforms=tools:windows_x64`, `@bazel_lib//lib:enable_runfiles`
evaluates to `False` unless `--enable_runfiles` is passed, causing
`aspect_rules_js` to generate the test launcher script with
`JS_BINARY__NO_RUNFILES=1`.

In `aspect_rules_js` 3.5.2, `JS_BINARY__NO_RUNFILES=1` resolves the
entry point using `JS_BINARY__BINDIR` (`bazel-out/k8-fastbuild/bin`)
instead of `BAZEL_BINDIR` (`.`), which fails on Windows CI where the
tests are executed from the built `.runfiles` directory tree. Passing
`--enable_runfiles` during the Windows E2E cross-build ensures the
launcher script resolves the entry point from the runfiles directory.

Author: alan-agius4

.github/workflows/ci.yml

@@ -118,7 +118,8 @@ jobs:
             --config=e2e \
             //tests:e2e.webpack_node24 \
             //tests:e2e.esbuild_node24 \
-            --platforms=tools:windows_x64
+            --platforms=tools:windows_x64 \
+            --enable_runfiles
       - name: Store built Windows E2E tests
         uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
         with:

.github/workflows/pr.yml

@@ -143,7 +143,8 @@ jobs:
           pnpm bazel build \
             --config=e2e \
             //tests:e2e.esbuild_node24 \
-            --platforms=tools:windows_x64
+            --platforms=tools:windows_x64 \
+            --enable_runfiles
       - name: Store built Windows E2E tests
         uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
         with: