In BF-34065 we saw a couple cases where writes done via persistCollectionAndChangedChunks interleaved with calls to serverStatus that are done to check metrics and so the "after" metrics end up reflecting more updates or deletes than expected (I think this could also be a problem for inserts as well though we haven't seen it yet.)

This is caused by the introduction of  SERVER-90864, which now causes createCollection to complete without installing filtering metadata in any of the data bearing nodes (this action will be now performed as part of the first read/write operation received).

The test setup part of server_write_concern_metrics_sharding.js needs to be adapted to this new behavior.