[Remote Segment Store] Use files from segmentInfosSnapshot in upload

[sachinpkale]

Description

• RemoteStoreRefreshListener is one of the refresh listeners that uploads segments to remote segment store.
• Currently, it reads segmentInfosSnapshot from InternalEngine and adds files referenced by segments_N file.
• This is a defensive approach that was taken so that we do not lose track of any segment file but this can create issue in scenarios such as forcemerge, where segmentInfosSnapshot is referencing to segments_N file but the files referenced by segments_N are merged away.
• In this PR, we use segment files referenced by segmentInfosSnapshot alone.
• Added integ tests around the forcemerge use case. Existing integ tests should pass.

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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: UNSTABLE ❕
• TEST FAILURES:

      2 org.opensearch.common.util.concurrent.QueueResizableOpenSearchThreadPoolExecutorTests.classMethod
      1 org.opensearch.common.util.concurrent.QueueResizableOpenSearchThreadPoolExecutorTests.testResizeQueueDown

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

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      2 org.opensearch.index.shard.RemoteStoreRefreshListenerTests.classMethod
      2 org.opensearch.cluster.service.MasterServiceTests.classMethod
      1 org.opensearch.indices.replication.SegmentReplicationIT.testPitCreatedOnReplica
      1 org.opensearch.index.shard.RemoteStoreRefreshListenerTests.testRefreshAfterCommit
      1 org.opensearch.cluster.service.MasterServiceTests.testThrottlingForMultipleTaskTypes
      1 org.opensearch.client.ReindexIT.testReindexTask

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

[sachinpkale]

Taking a look at test failures in org.opensearch.index.shard.RemoteStoreRefreshListenerTests

[sachinpkale]

New integ tests are executed 180+ times on local to avoid checking in flaky tests.

[ashking94]

LGTM.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.remotestore.SegmentReplicationRemoteStoreIT.testPressureServiceStats
      1 org.opensearch.remotestore.RemoteStoreIT.testStaleCommitDeletionWithInvokeFlush

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

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/20389/
• CommitID: cec103f
  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.remotestore.RemoteStoreIT.testStaleCommitDeletionWithInvokeFlush
      1 org.opensearch.index.IndexSettingsTests.testDefaultSearchPipelineWithoutFeatureFlag

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

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-8487-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 230a06daee9c8484e38d6aad867a98c3c10c2485
# Push it to GitHub
git push --set-upstream origin backport/backport-8487-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-8487-to-2.x.