timeseries_multiple_mongos.js is currently checking how many times a multi write without shard key is being executed in the cluster (for example here). This is not correct, multi writes are not atomic, meaning, some interleaving might cause them to be executed more than once, in this case, a hedge read to a secondary might cause the non primary db shard to refresh the metadata, accepting the update which will be sent with ShardVersion::IGNORED.

We should remove all writes without shard key from the test, that is, all updates and deletes with q: {}.