feat: Add retry logic to plugins download

[erezrokah]

Sometimes downloading of plugins fails due to a glitch with GitHub:
https://github.com/cloudquery/cloudquery/actions/runs/3243530449/jobs/5318376371#step:7:9

and a simple retry works.

We should add retry logic as to not fail in these cases

[cychiang]

Hi @erezrokah I would like to discuss this task with you. I found it a bit difficult to write test cases for downloading an artifact from GitHub. In order to mock a http request or response with []byte, for mocking http request it needs to create an interface for http.Client but mocking a response sounds too specific and not easy to extend in the future if needed. So I go around the code and what is inside the download.go and is basically:

• format url with inputs
• setup output location and file name
• save file
• show progressbar

Because create an interface and re-write some code with test cases take times so maybe can go for another way. I'm thinking to improve this part with go-resty and httpmock so we can have better handling for downloading files and proper test cases. But not sure is it worth to do it or not. 🤔 What do you think about this part? I'm still getting familiar with this project so any feedback are welcome.

[erezrokah]

Thanks for the PR @cychiang and pushing this issue forward. I commented on the PR and testing part in #310 (review)