Change default operator definition style to break after ==

[FedericoPonzi]

For operator definitions with conjunction/disjunction list bodies, the formatter now always places the body on the next line with fixed indentation, improving VS Code code folding support.

Before:

TypeInv == /\ x \in Nat
/\ y \in 0..N

After:

TypeInv ==
/\ x \in Nat
/\ y \in 0..N

Simple definitions (e.g., foo == 42) are unaffected.

Fixes: #20

@lemmy let me know if it LGTY how the specs are getting formatted so that I can merge this, thanks.

[lemmy]

To confirm, the changes suggests that there is indentation but your snippet above simply doesn't show it?

[FedericoPonzi]

Please check the exanples formatting from the diff. The description is extracted from the commit message, and I haven't used markdown there