Fix installation that causes torch conflict

[mergennachin]

When pip installs timm==1.0.7 (from requirements-examples.txt), it's pulling its dependencies from PyPI, and since the PyPI version of timm has a dependency on torch without any version constraints, pip is "upgrading" your nightly torch to the latest stable release from PyPI.

Here's what's happening:

I have torch==2.9.0.dev20250725 (nightly) installed
When pip installs timm, it sees that timm requires torch
Pip finds torch==2.7.1 on PyPI (the latest stable release)
Since 2.9.0.dev20250725 is considered a pre-release version, pip thinks 2.7.1 is "newer" in terms of stable releases
Pip uninstalls the nightly and installs the stable version.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

⏳ 193 Pending, 1 Unrelated Failure

As of commit 8acca36 with merge base 48e4822 ():

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

• pull / test-models-linux (add_mul, portable, linux.2xlarge) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128

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.

[mergennachin]

I think a simpler fix is this #13074