Retrying would be useful #244
Description
This is not happening frequently, but once in a while, we get an HTTP 504 Gateway Timeout server error response status code in GitHub Actions.
Ideally, this would be solved by having something akin to curl's --retry option.
ureq used to have such an option integrated, but this was removed in version 3. We could do something similar manually, but this would entail handling HTTP responses manually (see algesten/ureq#1142).
I am not sure what the best solution would be. For us, an optional GitHub-CLI-based gh release download would solve this. Being based on the GitHub CLI, this is not a very general solution, though.