[BUG] Retries disabled in HTTP client builder.

[aiswaryasridharan]

What is the bug?

HTTP client transport builder specifically disables retries. This requires workaround to be created in the business layer, which may not always be the most elegant way to perform these retries. Allowing the client builder the ability to provide a custom retry strategy will provide a more robust and efficient client. Not everybody is going to use retry strategies just because there is an ability to do so - so I think it should be left to the discretion of the software architect on whether to use a retry strategy and how it should be defined, rather than outright disabling the ability to retry at all.

How can one reproduce the bug?

Create a new HTTP transport.
Set a custom or default retry strategy in the builder.
None of the overridden retry request methods ever get called.

What is the expected behavior?

Allow retry strategies to be defined if they are deemed as required.

What is your host/environment?

Code running in an opensearch container. Running version 2.15.0.

Do you have any screenshots?

If applicable, add screenshots to help explain your problem.

Do you have any additional context?

Add any other context about the problem.

[andrross]

Catch All Triage - 1 2

@reta Do you have context as to why retries are specifically disabled here?