Prefetch all dev-env tools (#3409)

* Prefetch all dev-env tools

maybe this helps with some of the CI flakiness that we have seen.

* no enable

bazel_tools/dev_env_tool/dev_env_tool.bzl

@@ -41,7 +41,7 @@ config_setting(
 
 def _dadew_where(ctx, ps):
     ps = ctx.which("powershell")
-    ps_result = ctx.execute([ps, "-Command", "dadew enable; dadew where"], quiet = True)
+    ps_result = ctx.execute([ps, "-Command", "dadew where"], quiet = True)
 
     if ps_result.return_code != 0:
         fail("Failed to obtain dadew location.\nExit code %d.\n%s\n%s" %

build.ps1

@@ -32,7 +32,15 @@ bazel shutdown
 
 # Manually fetch a Windows dev-env tool to avoid the following error:
 #   ERROR loading ~/.scoop: The process cannot access the file 'C:\Users\VssAdministrator\.scoop' because it is being used by another process.
+bazel fetch @tar_dev_env//...
+bazel fetch @gzip_dev_env//...
+bazel fetch @mvn_dev_env//...
+bazel fetch @zip_dev_env//...
+bazel fetch @jq_dev_env//...
+bazel fetch @javadoc_dev_env//...
 bazel fetch @makensis_dev_env//...
+bazel fetch @nodejs_dev_env//...
+bazel fetch @postgresql_dev_env//...
 
 bazel build `-`-experimental_execution_log_file ${ARTIFACT_DIRS}/build_execution_windows.log //...