Build PyTorch wheel via PEP 517 instead of setup.py (#21562)

Recent PyTorch nightlies removed `python setup.py bdist_wheel`; PyTorch now builds through scikit-build-core via the standard PEP 517 interface. Build the wheel with `python -m build --wheel --no-isolation` so the CI docker image can pick up newer nightlies. No isolation keeps the build against the image's own numpy and toolchain and lets it reuse sccache, so the build requirements are installed explicitly. The wheel still lands in dist/, so the install step is unchanged.

Author: shoumikhin

.ci/docker/common/install_pytorch.sh

@@ -49,8 +49,18 @@ install_pytorch_and_domains() {
     export MAX_JOBS="${PYTORCH_BUILD_MAX_JOBS}"
   fi
   configure_pytorch_compiler
-  # Then build and install PyTorch
-  conda_run python setup.py bdist_wheel
+  # PyTorch no longer supports "python setup.py bdist_wheel"; it now builds
+  # through scikit-build-core (PEP 517). Build the wheel with the standard
+  # frontend and keep build isolation off, so PyTorch builds against this
+  # environment's numpy and toolchain (avoids an ABI mismatch) and reuses
+  # sccache. With isolation off the frontend does not fetch the PEP 517 build
+  # requirements, so install the ones not already in the image here. Keep in
+  # sync with pytorch/pyproject.toml [build-system].requires.
+  # cmake stays below 4 because the wheel lands on PATH ahead of the image's
+  # cmake 3.x, so every later build in the image would jump a major version.
+  conda_run pip install build "scikit-build-core>=1.0" "setuptools>=77.0.0,<82" \
+    "cmake>=3.27,<4" ninja "packaging>=24.2" "typing-extensions>=4.10.0" pyyaml six
+  conda_run python -m build --wheel --no-isolation
   pip_install "$(echo dist/*.whl)"
 
   # Grab the pinned audio and vision commits from PyTorch