Add load('implicitly_shard_accessed_collections.js') to worker_thread.js if args.sessionOptions.readPreference is set. This ticket will involve investigating workloads that may be incompatible with the override and need to be blacklisted.

Some known blacklists are:

• explain*.js workloads - they assert a collection does not exist, but the override may recreate it
• reindex*.js workloads - they make assertions on the number of indexes, but an extra one will be created for {_id: "hashed"}

Potential blacklists:

• drop_collection.js
• kill_rooted_or.js, kill_aggregation.js

These workloads frequently timeout waiting for the distributed lock, which may be related to the override causing more load on the config server