The code in __lsm_merge_span is confusing when attempting to understand what youngest_gen and youngest variables track.

The youngest_gen variable appears to sensibly track what the variable name implies, but youngest appears to track the chunk currently being considered. We should update the code so that it's intent is clearer.