As mentioned in  SERVER-32553 removeShard in jstests can be problematic due to stepdown of the config server which may lead to a ShardNotFound.

In several places a snipped code like the following https://github.com/10gen/mongo/blob/527dfe85a1771586339b34a177b3f7954aa2793b/jstests/sharding/data_size_aware_balancing_sessions_collection.js#L65-L82 has been used to prevent test from failing. 

after SERVER-67734 a utility script was added https://github.com/10gen/mongo/blob/master/jstests/sharding/libs/remove_shard_util.js

that allows you to safely run a removeShard until the process returns 'complete'

all the snippet codes can now be safely replaced with the utility removeShard. 

This should encourage developers to run the utility removeShard ad prevent another BF for the same reason