Feature/add configurable retry

[alexbourret]

Fixing issue 84

[MayeulRousselet]

[sc-333727]

[duynghiatran]

The retry mechanism is great, but it currently counts the total retry per dataset, not per row. Is this intentional? Here in my example, the first request took 5 secs, but all other requests took only 1s because the first one was retried 5 times, and all the others are not

[yannickbetou-dku]

What you are trying to do works as expected but I see multiple important issues :

1. The retries goes over the "Rate limit (requests/m)" parameter :

• If I configure a rate limit of 1 requests per minutes, and retries every 1 seconds, it will still send a request every 1 seconds, removing the purpose of rate limiting.

2: I think "502 bad gateway" should be added to the list of http codes, it tends to happen a lot when services are not reachable

3: I think we should manage the "Retry-After" header that is usually sent back in case of 429 response. It makes no sense to retry directly if the service told us to retry after X seconds.