Fix RemoteCloneIndex flaky test by using sync FS repo

[gbbafna]

Description

If we use async FS Repo , checksum comes null in a flaky way . To stop further build failures, i have set it to not use async FS Repo . This is what we are doing for RemoteSplitIndexIT as well and originally done in #13637

The tricky thing is i am not able to repro why the checksum could come null even on 2.5k iterations and running . I will keep running this to see if it ever fails .

Related Issues

Resolves #14292

Check List

• Functionality includes testing.
• [ ] API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

❌ Gradle check result for 464b4bf: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 464b4bf: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for ac4e6a0: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for c903bef: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for ac4e6a0: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for c903bef: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[gbbafna]

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':distribution:bwc:minor:buildBwcLinuxTar'.
> Building 2.16.0 didn't generate expected file /var/jenkins/workspace/gradle-check/search/distribution/bwc/minor/build/bwc/checkout-2.x/distribution/archives/linux-tar/build/distributions/opensearch-min-2.16.0-SNAPSHOT-linux-x64.tar.gz

Getting build failures despite branch up to date with mainline.

[gbbafna]

Looks like other build are also facing same issue . This is happening locally as well .

[github-actions]

❌ Gradle check result for 77a9bf9: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for 77a9bf9: SUCCESS

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.77%. Comparing base (48634bd) to head (77a9bf9).
Report is 3 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #15037      +/-   ##
============================================
- Coverage     71.82%   71.77%   -0.06%     
- Complexity    62778    62810      +32     
============================================
  Files          5169     5169              
  Lines        294646   294665      +19     
  Branches      42610    42616       +6     
============================================
- Hits         211644   211497     -147     
- Misses        65573    65800     +227     
+ Partials      17429    17368      -61     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.