[FEATURE] Add retries to the internal httpx.Client used by the SDK

[gabrielmbmb]

Description

This PR adds a new argument retries that can be used to specify the number of times that an HTTP request performed by the internal httpx.Client used by the SDK should be retried before raising an exception.

This is useful as sometimes while using the dataset.records.log you can receive a ConnectionError or 5xx from the server and if you retry a few seconds later everything is fine.

Type of change

• Improvement

How Has This Been Tested

Checklist

• I added relevant documentation
• I followed the style guidelines of this project
• I did a self-review of my code
• I made corresponding changes to the documentation
• I confirm My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

[davidberenstein1957]

@gabrielmbmb should we define upon which failures we retry. I think it only makes sense for the 500 series and perhaps on request timeout or anything. https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#client_error_responses
if payload is invalid or something, we don't want to retry.

[davidberenstein1957]

@gabrielmbmb I think we can add this to the constants.py file.

[burtenshaw]

@gabrielmbmb The refactor of timeout and retries looks good to me. It's more consistent and avoids background passing with **client_args.

@davidberenstein1957 A few PRs have used constants in context lately. I think we should tackle this in a dedicated PR because using a single constant file is not universally good.

[burtenshaw]

@gabrielmbmb Implementation looks good. What do you think about expanding the testing for this? I thought of these two but open to your suggestions:

• One unit for retries attributes in here argilla/tests/unit/api/http/test_http_client.py.
• One using pytest_httpx mock and checking the number of retries. Documented here

[burtenshaw]

@frascuchon @davidberenstein1957 What's your view of this PR? I've added a test and the remaining comments are:

• variables in module or shared constants
• dealing with 50* errors

[davidberenstein1957]

@frascuchon @davidberenstein1957 What's your view of this PR? I've added a test and the remaining comments are:

• variables in module or shared constants
• dealing with 50* errors

I think there are several error that can occur and will never be fixed by retries, like authentication or wrong payload, so for me it doesn't make sense to retry during those cases.

W.r.t. variables vs shared constants, I don't have a strict opinion besides having everything else in constants.py already.