This ticket should do following things
1. Recipient state machinery should add the backup cursorID info into the R state document.
2 .New R primary after failover should start the backupCursorStartAlive Thread using backup cursorID info. (We agreed that Shard Merge is not robust to donor/recipient failovers, restarts and rollbacks in the initial release.)