Bump PyTorch and TorchAO pins for dev20261004

[pytorchupdatebot]

Summary

Automated weekly PyTorch and TorchAO pin bump.

• Updates NIGHTLY_VERSION in torch_pin.py to dev20261004
• Updates .ci/docker/ci_commit_pins/pytorch.txt to the corresponding nightly commit hash
• Syncs c10 headers from PyTorch into runtime/core/portable_type/c10/
• Updates the TorchAO nightly pins and third-party/ao to the newest build available for every supported CUDA channel

This PR was created automatically. If CI fails, Claude will attempt to fix issues (up to 3 attempts). If CI still fails, human review will be requested.

cc @jakeszwe

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/23406

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 5 Cancelled Jobs, 1 Pending, 1 Unrelated Failure

As of commit 8f7a437 with merge base 5e21c13 ():

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• pull / test-qnn-direct-build-linux / linux-job (gh)
  ##[error]received SIGINT
• pull / test-qnn-passes-linux / linux-job (gh)
  [runner-container-hooks] FATAL: received SIGINT
• pull / test-qnn-python-imports-linux / linux-job (gh)
  Pod mt-l-x86iavx512-8-64-r6gdl-runner-jfvdh-workflow: phase=Pending, conditions=[PodReadyToStartContainers=True, Initialized=True, Ready=False, ContainersReady=False, PodScheduled=True], waiting=[job: ErrImagePull] (51s/7200s)
• trunk / test-demo-backend-delegation (buck2) / linux-job (gh)
  ##[error]received SIGINT
• trunk / test-demo-backend-delegation (cmake) / linux-job (gh)
  [runner-container-hooks] FATAL: received SIGINT

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• trunk / test-samsung-models-linux / linux-job (gh) (trunk failure)
  test_yolo26

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.