[Remote Store] Abstract out remote segment garbage collection logic

[sachinpkale]

Description

• Currently, remote segment garbage collection is tightly coupled with RemoteStoreRefreshListener and has a fixed logic where the deletion is triggered post commit.
• Ideally, garbage collection should be a separate flow and should not be coupled with RemoteStoreRefreshListener.
• It is also possible to have different triggers to the garbage collection like time based, size based etc.
• It shold also be possible to turn off the garbage collection completely where user wants to control it externally.
• In this PR, logic for remote segment garbage collection is abstracted out from RemoteStoreRefreshListener.

Related Issues

• [Feature Request] Abstract out remote segemnt garbage collection #13223

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]

Compatibility status:

Checks if related components are compatible with change cc805f9

Incompatible components

Skipped components

Compatible components

[github-actions]

❌ Gradle check result for cc805f9: 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 cc805f9: 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?

[Bukhtawar]

Maybe a better contract would be shouldGarbageCollect() that returns a boolean. We can add additional safety constraints explicitly

[opensearch-trigger-bot]

This PR is stalled because it has been open for 30 days with no activity.