+str #15079 Add flexible merge

Still only a prototype, but would be great with a round of feedback for tomorrow's work.

I tried the "return next behavior" approach (see savepoint1 if you are interested), but that was a dead end. We want to allow return of behavior with new input and output types, e.g. Zip, and I couldn't get that to work without explosion of types. Reverted back to become.

// cc @drewhk @sirthias 
just wondering idly: is the below the algorithm which is simply defined to be fair? because under uneven input rates I can imagine several different potential algorithms which can all reasonably claim to aim at fairness, just differently …