Currently ScopedSetShardRole which sets the shard version is scoped to affect the whole index build thread. This should not be necessary, and has caused issues in the past (SERVER-69530).

The shard version protocol is only required when setting up the index build and writing the 'startIndexBuild' oplog entry. If a chunk migration is in-progress while an index build is started, it will be aborted. A recipient shard will copy in-progress indexes from the donor shard, and if the index build is aborted on the donor, the client running createIndexes will receive an error requiring them to retry the command, and the indexes will become consistent.