Use cuda version PT when build with CUDA delegate

[Gasoonjia]

This PR enables CUDA version PT installation when building with CUDA delegate enabled from source.

More specific:

1. ET will keep depending on cpu PT as long as CUDA delegate is not enabled;
2. We will choose the CUDA PT exactly match user's cuda version: if user don't have CUDA, or have CUDA but not exactly match the versions PT supported, the installation script will raise error.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 4 New Failures, 7 Unrelated Failures

As of commit 19c2fb2 with merge base a548635 ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 9b9e9d6c06f46d5426b60877948ea53d136332a09ade1fef6122d384d00c086e /exec failed with exit code 1
• Test CUDA Builds / check-all-cuda-builds (gh)
  Process completed with exit code 1.
• Test CUDA Builds / test-executorch-cuda-build-12.9 / linux-job (gh)
  RuntimeError: Command docker exec -t 6efaecb9972e9758528b0ee2937f8d19bcd405be930b572d33c9786fc1444433 /exec failed with exit code 1
• trunk / test-arm-ootb-linux / linux-job (gh)
  RuntimeError: Command docker exec -t ae5f5b101bccc348a9d5ce9e11c1e0aa674d2796fd38a046dadafe024957288a /exec failed with exit code 1

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• docker-builds / docker-build (linux.2xlarge, executorch-ubuntu-22.04-gcc9) (gh) (detected as infra flaky with no log or failing log classifier)
• pull / test-binary-size-linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• pull / test-llama-runner-qnn-linux (fp32, qnn_8a8w, qnn) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• pull / test-models-linux (emformer_transcribe, portable, linux.2xlarge) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• pull / test-qnn-wheel-packages-linux (3.11) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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

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

• trunk / unittest-release / linux / linux-job (gh) (trunk failure)
  [ FAILED ] LoggingTest.Utf8Truncation
• trunk / unittest-release / macos / macos-job (gh) (trunk failure)
  [ FAILED ] LoggingTest.Utf8Truncation

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.

[larryliu0820]

Can we pull all cuda related functions into util?

[larryliu0820]

This seems like it belongs to util as well

[JacobSzwejbka]

this function is only called twice is it really necessary to cache?

[Gasoonjia]

main reason to cache is try not print too much noise output.

[larryliu0820]

Use @functools.lru_cache