To ensure shards eventually pick up the new shard key after a shard key refine, during _configsvrRefineCollectionShardKey an asynchronous task resilient to failover should be launched that is guaranteed to trigger a refresh for the refined collection if the shard key refine succeeds and becomes majority committed. This should use the PersistentTaskQueue from the resumable range deleter project.