The router will translate an update that would change the owning shard into an insert and delete. Currently query stats for updates do not get this right. I added a relevant test case as part of the work for SERVER-120403.

Current behavior is that the router receives a WCOS for the shard that owns the document (before its updated), and so no query stats are collected. When we begin collecting stats for inserts and deletes this may change.