When the chunk manager can contain both UUIDs and shard ids, callers which rely on a shardId in some way need to access the shard registry in order to resolve a shardId to a shardHandle in order to return a consistent result. This requires an opCtx and access to the shard registry, something that the chunk manager does not have today. In this ticket, we will simply do the manual work of piping the opCtx through the chunk manager callers without changing any behavior.

Note that because the chunk manager is in the s_common library while the shard registry is in the grid library, these changes will require adding a layer of indirection to the chunk manager accesses located in the grid, otherwise the chunk manager accessing the grid will cause circular dependencies.