Incorrect parsing of `&&` as two unary `&`

[akimd]

Hi,

In the following example (a) && (b > 0) is mistakenly parsed as a cast to type a of &(&(b > 0)).

Cheers.

$ echo 'res = (a) && (b > 0);' | tree-sitter parse --no-ranges
(compilation_unit
  (global_statement
    (expression_statement
      (assignment_expression
        left: (identifier)
        right: (cast_expression
          type: (identifier)
          value: (prefix_unary_expression
            (prefix_unary_expression
              (parenthesized_expression
                (binary_expression
                  left: (identifier)
                  right: (integer_literal))))))))))