Internally, the chunk manager will resolve ShardRefs to some consistent state when a function is called where this makes sense (primarily those where a ShardId is passed as input to the function). SERZVER-128987 updated these functions to take an operationContext as an argument to allow for this resolution.

However, there are some other functions in the chunk manager which do not have a clear resolution path or even a possible one. For example, the "forEachChunk" function can't really provide consistent shardRefs because what they should use may depend on the caller. This ticket is for addressing these functions, by going through callers and ensuring that (1) they use shardRef if they are accessing the shard element of the chunk type and (2) that whichever logic they have is robust to a mixed chunk map state.