fix(NODE-7512): work around Windows C:/Z: NTFS junction in CI scripts

On some Windows Evergreen hosts, install-node.sh resolves NODE_ARTIFACTS_PATH
to Z: (via realpath following an NTFS junction) but DRIVERS_TOOLS is always
set to C: by prepare-shell.sh. When run-tests.sh later calls
init-node-and-npm-env.sh via the C: path, NODE_ARTIFACTS_PATH gets recomputed
to C: and npm is not found.

Fix by persisting the correctly-resolved NODE_ARTIFACTS_PATH to
$DRIVERS_TOOLS/.env in install-dependencies.sh, and restoring it in
run-tests.sh if npm is inaccessible after init-node-and-npm-env.sh runs.

Author: tadjik1

.evergreen/install-dependencies.sh

@@ -12,6 +12,15 @@ if [ -z ${NODE_LTS_VERSION+omitted} ]; then echo "NODE_LTS_VERSION is unset" &&
 # be handled by this script in drivers tools.
 source $DRIVERS_TOOLS/.evergreen/install-node.sh
 
+# On Windows, install-node.sh resolves SCRIPT_DIR via realpath which may follow an NTFS
+# junction (e.g. C: -> Z:), so NODE_ARTIFACTS_PATH is now correctly set to the real drive.
+# Persist it to .env so that subsequent shells (e.g. run-tests.sh) can recover it even
+# when they call init-node-and-npm-env.sh via the C: DRIVERS_TOOLS path.
+if [ "${OS:-}" = "Windows_NT" ] && [ -n "${NODE_ARTIFACTS_PATH:-}" ]; then
+  echo "NODE_ARTIFACTS_PATH=${NODE_ARTIFACTS_PATH}" >> "${DRIVERS_TOOLS}/.env"
+fi
+_INSTALL_DEPS_NODE_ARTIFACTS_PATH="${NODE_ARTIFACTS_PATH:-}"
+
 if [ "$NATIVE" = "true" ]; then
   # https://github.com/nodejs/node-gyp#configuring-python-dependency
   . $DRIVERS_TOOLS/.evergreen/find-python3.sh
@@ -22,3 +31,10 @@ fi
 npm install "${NPM_OPTIONS}"
 
 source $DRIVERS_TOOLS/.evergreen/init-node-and-npm-env.sh
+# On Windows, the init call above may have overwritten NODE_ARTIFACTS_PATH with the wrong
+# drive letter.  Restore the previously resolved path if npm is no longer accessible.
+if [ "${OS:-}" = "Windows_NT" ] && [ -n "$_INSTALL_DEPS_NODE_ARTIFACTS_PATH" ] && ! command -v npm >/dev/null 2>&1; then
+  export NODE_ARTIFACTS_PATH="$_INSTALL_DEPS_NODE_ARTIFACTS_PATH"
+  export PATH="$NODE_ARTIFACTS_PATH/nodejs/bin:$PATH"
+  hash -r
+fi

.evergreen/run-tests.sh

@@ -36,7 +36,19 @@ echo "Running $AUTH tests over $SSL, connecting to $MONGODB_URI"
 if [[ -z "${SKIP_DEPS}" ]]; then
   source "${PROJECT_DIRECTORY}/.evergreen/install-dependencies.sh"
 else
+  # On Windows, DRIVERS_TOOLS is a C: path but Node may have been installed on Z: (NTFS
+  # junction).  Load NODE_ARTIFACTS_PATH written by install-dependencies.sh before calling
+  # init so we can restore it if init resolves to the wrong drive.
+  _RUN_TESTS_SAVED_NODE_PATH=""
+  if [ "${OS:-}" = "Windows_NT" ] && [ -f "${DRIVERS_TOOLS}/.env" ]; then
+    _RUN_TESTS_SAVED_NODE_PATH=$(grep '^NODE_ARTIFACTS_PATH=' "${DRIVERS_TOOLS}/.env" | tail -1 | cut -d= -f2-)
+  fi
   source $DRIVERS_TOOLS/.evergreen/init-node-and-npm-env.sh
+  if [ "${OS:-}" = "Windows_NT" ] && [ -n "$_RUN_TESTS_SAVED_NODE_PATH" ] && ! command -v npm >/dev/null 2>&1; then
+    export NODE_ARTIFACTS_PATH="$_RUN_TESTS_SAVED_NODE_PATH"
+    export PATH="$NODE_ARTIFACTS_PATH/nodejs/bin:$PATH"
+    hash -r
+  fi
 fi
 
 if [ "$COMPRESSOR" != "" ]; then