feat(compiler)!: Allow infix operators on new line

[alex-snezhko]

let x = 3
- 2
print(x) // 1

let x = 2
+1
-1 // Will give warning to ask for either a space after `-`, wrap in parens, or semicolon on prev line
print(x) // 3

let (|>) = (x, f) => f(x)
let a = [1, 2, 2, 3]
  |> List.reverse
  |> List.unique

[alex-snezhko]

@ospencer @phated I implemented the changes we discussed

[ospencer]

I'm not a fan of the changes to the parsetree. We should be able to have a fully semantic program without needing to read these extra properties, so that probably means we're not doing enough during parsing. We should be able to produce the error we want in the wrapped lexer.

[spotandjake]

Mostly looks good to me, I had a few formatting nits.

[spotandjake]

I feel like this formatting looks a little weird how would we feel about placing the operator on the top line in cases where a parens come first?

[spotandjake]

This comment formating doesn't seem right.

[spotandjake]

Reading through all the formatted code, I find it looks really wierd with the == on a newline mostly because its not often that you chain equals together I wonder if we should preserve the old formatting style for ==.

[spotandjake]

This comment being on the line below really feels like it changes the meaning of it. There has been a few cases like this.

[alex-snezhko]

@ospencer wouldn't that basically involve having an entire parser within wrapped_lexer? You'd need to know when you encounter a full expression within wrapped_lexer to know whether or not to give the warning