[Feature] Experimental: Make retry strategy configurable

[avijeet95]

Adds support to configure Retry Strategy in HttpClient. Currently only the default retry strategy is used. This strategy retries 3 times and does not have any sleep interval in between. For our use case, we would prefer using the ExponentialBackOffStrategy.

This does not affect the default behavior but gives additional options to the users.

[mgyucht]

Let's label this as experimental, but otherwise this is fine for me.

Long-term, I think we will want to implement retries at a higher layer, after the response is deserialized, so that the retry implementation can review a deserialized error response before making a decision.

[avijeet95]

Let's label this as experimental, but otherwise this is fine for me.

Long-term, I think we will want to implement retries at a higher layer, after the response is deserialized, so that the retry implementation can review a deserialized error response before making a decision.

Yes right now there are retries from the SDK level and then further in HttpClient. But making that decision is a bit more involved so this PR unblocks us till we get to the point you suggested. Thanks!

[avijeet95]

Added experimental to list of valid tags

[mgyucht]

Ah sorry, I meant to label withRequestRetryHandler as experimental in a doccomment. The PR tags need to be consistent across all SDKs to minimize unnecessary variance. Let's set the PR title to[Feature] Experimental: Make retry strategy configurable.