[Feature Request] Abstract out remote segemnt garbage collection

[sachinpkale]

Is your feature request related to a problem? Please describe

• 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.

Describe the solution you'd like

• Abstract out logic for remote segment garbage collection where a specific garbage collection implementation can be plugged without changing RemoteStoreRefreshListener.

Related component

Storage:Remote

Describe alternatives you've considered

No response

Additional context

No response