[NEW] Add Module APIs to support Atomic Slot Migration
The problem/use-case that the feature addresses
For modules like Search that have data that is related to key data (e.g., search indexes), when a slot migration happens there is not opportunity for the module to ensure that the "related" data update is properly synchronized to the slot migration machinery and the transfer of slot ownerships.
Description of the feature
Having module APIs that allow a module to keep it's "related" data synchronized to the slot ownership transfers.
Alternatives you've considered
Throttling of commands ingested through a slot migration client allows the target to prevent the gap between related data and the Valkey key data to from becoming too large. This helps reduce the window of unsynchronized data but doesn't eliminate it.
Additional information
Any additional information that is relevant to the feature request.