Fix flaky test testSendCorruptBytesToReplica

[mch2]

Description

This test is failing with WindowsFS.
This change moves SegRep corruption tests to a separate IT class and skips running on WindowsFS.

Related Issues

Resolves #10542
Resolves #10709

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28933/
• CommitID: 91bd1e9
  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?

[mch2]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28935/
• CommitID: 91bd1e9
  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?

#10899 again

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28938/
• CommitID: 91bd1e9
  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?

[mch2]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28938/
• CommitID: 91bd1e9
  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?

#10885

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28939/
• CommitID: 91bd1e9
  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?

[mch2]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28939/
• CommitID: 91bd1e9
  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?

#10902

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28943/
• CommitID: 91bd1e9
  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?

[mch2]

#10902

#10902

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28946/
• CommitID: 91bd1e9
  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?

[mch2]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28946/
• CommitID: 91bd1e9
  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?

#10903

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28951/
• CommitID: 91bd1e9
  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?

[mch2]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28951/
• CommitID: 91bd1e9
  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?

....another one #10899

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28955/
• CommitID: 91bd1e9
  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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28959/
• CommitID: 91bd1e9
  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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28982/
• CommitID: 91bd1e9
  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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28985/
• CommitID: 91bd1e9
  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 (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.snapshots.DedicatedClusterSnapshotRestoreIT.testIndexDeletionDuringSnapshotCreationInQueue

• URL: https://build.ci.opensearch.org/job/gradle-check/28997/
• CommitID: f155d9c
  Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[codecov]

Codecov Report

Merging #10897 (f155d9c) into main (5a288ed) will decrease coverage by 0.01%.
Report is 8 commits behind head on main.
The diff coverage is 72.93%.

@@             Coverage Diff              @@
##               main   #10897      +/-   ##
============================================
- Coverage     71.22%   71.21%   -0.01%     
- Complexity    58678    58701      +23     
============================================
  Files          4869     4872       +3     
  Lines        276496   276682     +186     
  Branches      40203    40219      +16     
============================================
+ Hits         196936   197044     +108     
- Misses        63114    63202      +88     
+ Partials      16446    16436      -10     

Files	Coverage Δ
...search/repositories/s3/AmazonAsyncS3Reference.java	84.61% <100.00%> (+1.28%)	⬆️
.../repositories/s3/AmazonAsyncS3WithCredentials.java	100.00% <100.00%> (ø)
...org/opensearch/repositories/s3/S3AsyncService.java	72.28% <100.00%> (+1.09%)	⬆️
...va/org/opensearch/repositories/s3/S3BlobStore.java	68.75% <100.00%> (+0.49%)	⬆️
...a/org/opensearch/repositories/s3/S3Repository.java	70.08% <100.00%> (+0.25%)	⬆️
...search/cluster/coordination/CoordinationState.java	88.39% <ø> (ø)
.../org/opensearch/cluster/service/MasterService.java	84.51% <100.00%> (-0.56%)	⬇️
...h/common/blobstore/stream/write/WritePriority.java	100.00% <100.00%> (ø)
...nsearch/gateway/remote/RemotePersistenceStats.java	100.00% <100.00%> (ø)
...epositories/blobstore/ChecksumBlobStoreFormat.java	95.45% <100.00%> (+0.29%)	⬆️
... and 12 more

... and 469 files with indirect coverage changes