Publish cuda-pathfinder to the torch CUDA arch indexes

torch declares cuda-bindings, and cuda-bindings requires
cuda-pathfinder>=1.4.2. Release smoke tests install from a single arch index
with no PyPI fallback, so that transitive dependency has to be resolvable
there too.

cuda-pathfinder was registered under the vllm project only, so
update_dependencies.py never wrote whl/{test,nightly}/cu*/cuda-pathfinder/.
whl/test/cu134 advertises it in the PEP 503 listing while the target 403s. The
older arches still serve it, but that is residue from before it stopped being
produced -- nothing regenerates it today, so cu134 is simply the first arch
created after that.

Give it the same torch targets as cuda-bindings, since it exists to satisfy
cuda-bindings. cuda-python is left alone: torch never depends on it, so its
absence from the arch indexes is correct.

Author: atalman

s3_management/update_dependencies.py

@@ -768,7 +768,33 @@
     # vLLM
     "ninja": [{"project": "vllm"}],
     "cuda-python": [{"project": "vllm"}],
-    "cuda-pathfinder": [{"project": "vllm"}],
+    "cuda-pathfinder": [
+        {
+            "project": "torch",
+            "target": "cu126",
+        },
+        {
+            "project": "torch",
+            "target": "cu128",
+        },
+        {
+            "project": "torch",
+            "target": "cu129",
+        },
+        {
+            "project": "torch",
+            "target": "cu130",
+        },
+        {
+            "project": "torch",
+            "target": "cu132",
+        },
+        {
+            "project": "torch",
+            "target": "cu134",
+        },
+        {"project": "vllm"},
+    ],
     "pynvml": [{"project": "vllm"}],
     "nvidia-ml-py": [{"project": "vllm"}],
     "einops": [{"project": "vllm"}],