introduce torch pin check

[Gasoonjia]

This PR adds a ci to check the consistency between .ci/docker/ci_commit_pins/pytorch.txt and torch_pin.py

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• [ROCm][CI] Machines under the label linux.rocm.gpu.2 are undergoing maintenance.

❌ 4 New Failures, 4 Unrelated Failures

As of commit 4edbba4 with merge base dbd0e9f ():

NEW FAILURES - The following jobs have failed:

• check-pytorch-pin / check-pytorch-pin (gh)
  Process completed with exit code 1.
• Lint / android-java-format / linux-job (gh)
  RuntimeError: Command docker exec -t 80890b798e6b617f800e3b20428c61f5338a24ce7b0ba97610105d7c80fec0c3 /exec failed with exit code 1
• Lint / lintrunner / linux-job (gh)
  >>> Lint for .ci/scripts/check_pytorch_pin.py:
• trunk / test-arm-backend (test_pytest_ops_ethosu_fvp) / linux-job (gh)
  RuntimeError: Command docker exec -t f91b8764d32413cf0b582f9db2894b42f3b029ef52625b36a5f37664c88dc790 /exec failed with exit code 1

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• trunk / test-multimodal-macos (gemma3-4b) / macos-job (gh) (detected as infra flaky with no log or failing log classifier)

BROKEN TRUNK - The following jobs failed but was present on the merge base:

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

• pull / unittest / windows / windows-job (gh) (trunk failure)
  runtime/test/test_runtime_etdump_gen.py::RuntimeETDumpGenTest::test_etdump_params_with_bytes_and_buffer
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  runtime/test/test_runtime_etdump_gen.py::RuntimeETDumpGenTest::test_etdump_params_with_bytes_and_buffer
• trunk / unittest-release / windows / windows-job (gh) (trunk failure)
  runtime/test/test_runtime_etdump_gen.py::RuntimeETDumpGenTest::test_etdump_params_with_bytes_and_buffer

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.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.