Mixed plain- and Result-pipelines are formatted poorly

[ag-eitilt]

I gave confusing commentary on mixed pipelines previously; I don't think they're necessarily good style and I'd personally be hard-blocking anything which went back to plain pipelines after the result arrows, but for short cases where there's less chance of getting lost in the types I can see the utility over requiring an extra def just for form.

More broadly, I want to differentiate formatter bugs from style concerns -- like I said in #1470 (which is worse than this), even if people shouldn't do something, if it's legal the formatter should still be able to handle it. Obviously not with as great a priority if supporting some discouraged construct winds up requiring a lot of specialized formatter casing, but if it's minimal work it would still be ideal to give an at-least-passible output.

With that said, it shouldn't matter what pipeline operator is used, a mixed block of piping should still be uniformly linebroken.

-        someValue | functionThatReturnsResult
+        someValue
+        | functionThatReturnsResult
         |> anotherFunctionThatReturnsResult