Freeze an outer projected row in pipelined case

Conceptually similar to 54a406f891d3de31504baff74d5cd8147905d0b8. Except that this has to happen even more often because much more is asynchronous. That only had to do it in the odd case of the row escaping the whole loop. This is any time it is bound as the outer row, because that means entering a pipeline from which it may not emerge for some time.

Both Map changes and several Sort changes all have the same root case. Which is that ```ProjectedRow``` has both shared evaluators and delayed evaluation. That is, quite simply, a recipe for disaster.

e24ce2fa8121510063988c27804b0cea4dfd070c probably should have removed the delayed evaluation, if shared evaluators were judged more important. Then 1cdd75707f86d61c389390ebde1623c24e88df5d and everything after it would have been unnecessary.

This branch does not propose to fix that, but just the latest manifestation.