Enable Bazel runfiles on Windows with widened test surface (#48206)

Prior art:
1. #48082
2. #48087
3. #48188 (1st attempt)
4. #48207
5. #48281
6. #48209

### What does this PR do?
This is a redo of #48188 (preemptively reverted by #48207) and therefore merely consists in re-adding `common:windows --enable_runfiles` to `.bazelrc`.

... with lessons learned, thanks to earlier:
- #48209 covers the present change to `.bazelrc`,
- #48281 prevents `find_python.bat` from falling back to `NuGet` or other non hermetic sources.

.... and now a widened `bazel:test:windows-amd64`, evolving from just `//bazel/tests/... //rtloader/...` to `//...` **- except currently failing targets** (for the time being, of course).

### Motivation
Summary of #48188:
- `rules_python` 1.9.0 (#48082) transitions every `py_binary` and `py_test` on Windows from `enable_runfiles=auto` to `enable_runfiles=true`,
- with Bazel's default (`enable_runfiles=false` on Windows), this creates a second Bazel configuration, causing
`python_win` to be built twice concurrently,
- `build_python.bat` writes `MSBuild` intermediates to the shared execroot source tree rather than the action's output directory, so both builds race on those files, causing [intermittent failures](https://gitlab.ddbuild.io/DataDog/datadog-agent/-/jobs/1533753039) (`pyconfig.h` not found, etc.).

**Pre-setting `--enable_runfiles` makes the transition a no-op, so Bazel sees a single configuration and builds `python_win` once.**

### Describe how you validated your changes
Local VM and, of course, CI.

### Additional Notes
For instance, `//pkg/template/...` is excluded on Windows because `gopatch` errors on `@@\r` in hunk markers when patch files have CRLF line endings, which deserves a distinct PR (likely adjusting `.gitattributes`).


Co-authored-by: regis.desgroppes <regis.desgroppes@datadoghq.com>

Author: rdesgroppes

.bazelrc

@@ -41,6 +41,9 @@ common:macos --remote_local_fallback_strategy=sandboxed
 
 # Windows config -------------------------------------------------------------------------------------------------------
 common:windows --strategy=standalone # Valid values are: [dynamic_worker, standalone, dynamic, remote, worker, local]
+# rules_python 1.9.0 transitions enable_runfiles to `true` for every py_ target on Windows. Pre-setting it here makes
+# that transition a no-op, so Bazel deduplicates python_win and avoids 2 concurrent MSBuild racing on shared resources.
+common:windows --enable_runfiles
 # Neither repo_env nor shell_executable affect action keys. It can be both an advantage and a disadvantage.
 # For instance, if we need to have some special behavior in bash we can add it, however, in some cases
 # it may lead to cache poisoning.

.gitlab/build/bazel/test.yml

@@ -26,5 +26,19 @@ bazel:test:macos-arm64:
 bazel:test:windows-amd64:
   extends: [ .bazel:test, .bazel:runner:windows-amd64 ]
   variables:
-    POWERSHELL_SCRIPT: |-
-      bazel test //bazel/tests/... //rtloader/...
+    POWERSHELL_SCRIPT: >-
+      bazel test //... --
+      -//bazel/rules/dd_packaging/...
+      -//internal/tools/modparser:modparser_test
+      -//internal/tools/worksynchronizer:worksynchronizer_test
+      -//packages/agent/linux/...
+      -//pkg/collector/corechecks/ebpf/probe/...
+      -//pkg/dyninst/loader/...
+      -//pkg/dyninst/output/...
+      -//pkg/ebpf/...
+      -//pkg/gpu/ebpf/...
+      -//pkg/network/...
+      -//pkg/networkdevice/profile/profiledefinition/schema:schema_test
+      -//pkg/template/...
+
+# //pkg/template:generate_N_test: TODO(regis) .gopatch files seem to be altered by .gitattributes

MODULE.bazel

@@ -224,7 +224,7 @@ register_toolchains(
 visual_studio(
     name = "visual_studio",
     path_variable = "VSTUDIO_ROOT",
-    version = "17.14.36717.8",
+    version = "17.14.36717.8",  # 18.4.11612.150
 )
 
 # =========================================