[HUDI-8988] Implement retry logic for all HTTP calls to timeline server including remote file system view and markers

[linliu-code]

Change Logs

We have rolled back timeline based marker and are using direct markers for product due to an issue we have hit a few times, stacktrace shown in the ticket (NoHttpResponseException). The RCA is that there are no retries, and the requests may sometimes get assigned to a connection pool with a broken connection and fail. This is an issue specific to fluent HTTP client, and can be solved using retries.

Impact

It changes the code path for timeline network calls for Remote File System View and Markers.

Risk level (write none, low medium or high below)

Medium.

Documentation Update

Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

• The config description must be updated if new configs are added or the default value of the configs are changed
• Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
  ticket number here and follow the instruction to make
  changes to the website.

Contributor's checklist

• Read through contributor's guide
• Change Logs and Impact were stated clearly
• Adequate tests were added if applicable
• CI passed

[hudi-bot]

CI report:

• bc30300 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build