In SERVER-84470 we made it so that $lookup and $graphLookup are supported on sharded collections. As part of this we had to modify the view_catalog_cycle_lookup.js test to ignore CursorNotFound errors which get triggered by the internal mergeCursor stage failing.

This error can occur during remappings of the underlying view but we haven't exactly pointed out why it occurs. In the case we can't handle the error in mongos and must return something to the user the error should not be confusing. Right now this is failing with a misleading CursorNotFound even if the cursor the user sent is still valid in the mongos layer.