Segment replication cancellation of in-sync allocation ids in ReplicationTracker

[dreamer-89]

Coming from #6761 exercise, RecoveryWhileUnderLoadIT.testRecoverWhileRelocating fails due to missing replication files from target store, failing assertion. This happens due to cancellation of segment replication, followed by replica shard failure, where engine's close action clears the temporary replication files.

Existing cancellation logic works on routing table changes and cancels segment replication for allocation ids which are not part of cluster metadata's in-sync ids. This can be problematic for cases where shard allocation just marked in-sync is not yet applied on cluster state.

[DarshitChanpura]

@dreamer-89 Closing this issue as it was fixed via #7214 and backported to 2.x line via #7220 & #7221. Feel free to re-open it.