Revert the inductor static launcher workaround

Switching to triton's own launcher only changed the message: the same
three DTensor mul tests fail at the same point, now with "Pointer
argument (at 0) cannot be accessed from Triton (cpu tensor?)" instead of
"CUDA driver error: invalid argument". The launcher was not the cause,
so drop the override rather than carry an env var that claims a fix.

Author: bhimrazy

.lightning/workflows/all-tests.yaml

@@ -93,10 +93,6 @@ run: |
         --timeout=360 \
         --numprocesses=9
   elif [ "${testing}" == "distributed" ]; then
-    # The DTensor tests build their reference with plain torch.compile, and on this image inductor's
-    # static Triton launcher dies there with "CUDA driver error: invalid argument" before thunder is
-    # ever reached. Fall back to Triton's own launcher until the image's torch/triton pairing is fixed.
-    TORCHINDUCTOR_USE_STATIC_CUDA_LAUNCHER=0 \
     pytest thunder/tests/distributed \
      -v --durations=0 \
      --random-order-seed=42