Format PatternMatchOr

[LaBatata101]

Summary

There was only one case where I couldn't figure it out how to format properly, which is the following

match x:
    case (
        (a)
        | # trailing
        ( b )
    ):
        ...

That code is being formatted to this

match x:
    case (
        (
            a  # trailing
        )
        | (b)
    ):
        ...

But it should be formatted to this

match x:
    case (
        (a)  # trailing
        | (b)
    ):
        ...

Closes #6643

Test Plan

cargo test

[LaBatata101]

Now clippy complains about not_yet_implemented_custom_text never being used. Should this function be removed?

And look at that amount of lines removed ☺️

[codspeed-hq]

CodSpeed Performance Report

Merging #6905 will not alter performance

_{Comparing LaBatata101:format-pattern-match-or (25e5224) with main (eae59cf)}

Summary

✅ 16 untouched benchmarks

[MichaReiser]

Now clippy complains about not_yet_implemented_custom_text never being used. Should this function be removed?

And look at that amount of lines removed ☺️

Finally, our last syntax is now implemented. Yes, we can remove that function.

[MichaReiser]

Neat! Thanks for working on the last pattern.

[MichaReiser]

Nice!

[MichaReiser]

Using the in_parentheses_only builder here seems correct but isn't sufficient without using optional_parentheses in the match case formatting. I created an issue to track that work #6933

[MichaReiser]

This PR improves the similarity index for CPython from cpython 0.76076 to 0.76081