ci: force-disable compute-sanitizer on PR matrix (debug only)

Wire the existing SETUP_SANITIZER gate behind a literal `false &&` so
every PR test job exports SETUP_SANITIZER=0 and SANITIZER_CMD=, which
makes run-tests invoke pytest directly instead of under
compute-sanitizer. Pairs with the matrix trim in this branch to test the
hypothesis that the TestIpcReexport hang on r595-driver runners is
specific to running pytest under compute-sanitizer. Revert before
merging.

Author: Andy-Jost

ci/tools/env-vars

@@ -88,7 +88,10 @@ elif [[ "${1}" == "test" ]]; then
   # We don't test compute-sanitizer on CTK<12 because backporting fixes is too much effort
   # We only test compute-sanitizer on python 3.12 arbitrarily; we don't need to use sanitizer on the entire matrix
   # Only local ctk installs have compute-sanitizer; there is no wheel for it
-  if [[ "${PY_VER}" == "3.12" && "${CUDA_VER}" != "11.8.0" && "${LOCAL_CTK}" == 1 && "${HOST_PLATFORM}" == linux* ]]; then
+  # TEMPORARY: force-disable compute-sanitizer to test whether it is the
+  # cause of the TestIpcReexport hang on r595-driver runners. Revert before
+  # merging.
+  if false && [[ "${PY_VER}" == "3.12" && "${CUDA_VER}" != "11.8.0" && "${LOCAL_CTK}" == 1 && "${HOST_PLATFORM}" == linux* ]]; then
     echo "LATEST_CUDA_VERSION=$(bash ci/tools/guess_latest.sh $TEST_CUDA_MAJOR)" >> $GITHUB_ENV
     SETUP_SANITIZER=1
   else