Retry all curl errors

[GregoryComer]

Summary

Update curl commands in CI scripts to retry all errors. This will hopefully improve CI reliability by reducing download failures.

A common pattern from CI logs is the following. Note that the failure is not retried.

+++ curl --retry 3 --retry-delay 5 --retry-connrefused --continue-at - -Lo /tmp/android-ndk-r26c-linux.zip https://dl.google.com/android/repository/android-ndk-r26c-linux.zip
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0  637M    0 1280k    0     0  3727k      0  0:02:55 --:--:--  0:02:55 3720k
  2  637M    2 13.0M    0     0  9928k      0  0:01:05  0:00:01  0:01:04 9923k
  4  637M    4 29.9M    0     0  12.7M      0  0:00:50  0:00:02  0:00:48 12.7M
  4  637M    4 31.2M    0     0  7724k      0  0:01:24  0:00:04  0:01:20 7725k
curl: (92) HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)

https://github.com/pytorch/executorch/actions/runs/26048331262/job/76578254537#step:17:17111

Most of the curl commands in our scripts do retry, but only certain types of errors. Switching to --retry-all-errors should hopefully be more robust to flakes. If something is hard down, it may spending ~15s retrying, but that's fine.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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:

• Run pull request jobs on OSDC runners in shadow mode

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