fix: handle ellipsis before <-, ::, and when

Ellipsis standalone detection used is_binary_op?/1, but that set did not include in_match_op, type_op, or when_op. As a result, expressions like x...<-y and x...::y attempted to parse <-/:: as an ellipsis RHS prefix and failed with unknown token errors.

Extend @binary_op_types with when_op, in_match_op, and type_op so parse_ellipsis_op/1 keeps ... standalone before those operators, matching Elixir AST behavior.

Add regression assertions in the existing property regression block for x...<-y, x...::y, and x... when y alongside the newline ternary case.

Author: mkaput

lib/spitfire.ex

@@ -1756,6 +1756,9 @@ defmodule Spitfire do
     :rel_op,
     :arrow_op,
     :in_op,
+    :when_op,
+    :in_match_op,
+    :type_op,
     :xor_op,
     :ternary_op,
     :concat_op,

test/spitfire_test.exs

@@ -2300,6 +2300,11 @@ defmodule SpitfireTest do
       assert Spitfire.parse("%e.(){}") == s2q("%e.(){}")
       assert Spitfire.parse("%e.(1){}") == s2q("%e.(1){}")
       assert Spitfire.parse("%e.(a, b){}") == s2q("%e.(a, b){}")
+
+      # Ellipsis followed by infix operators that should not be consumed as RHS
+      assert Spitfire.parse("x...<-y") == s2q("x...<-y")
+      assert Spitfire.parse("x...::y") == s2q("x...::y")
+      assert Spitfire.parse("x... when y") == s2q("x... when y")
     end
   end