Differentiate between identifier( and identifier<space>(

After an identifier, check if it is immediately followed by `(`.  If `(`
does follow, return a zero-width `CALL` token before the
`OPENING_PARENTHESIS` token for the `(`.
Quick fix for NoParanthesesStrict inspection

Alt+Enter on an ambiguous parentheses error will remove the space before
the space between the function name and the parentheses, which will fix
the annotated error.
matched_expr -> capture_op_eol no_parens_expr

Merge `matched_expr -> capture_op_eol matched_expr`, which already exists
as `matchedExpressionCaptureOperation ::= CAPTURE_OPERATOR EOL*
matchedExpression`, and `matched_expr -> capture_op_eol no_parens_expr`
into `matchedExpressionCaptureOperation ::= CAPTURE_OPERATOR EOL*
(noParenthesesExpression | matchedExpression)`.  Rearranged Capture.txt
so that the failing association operator test was at the end of the file
so it doesn't mask failures in the other operator precedence.
Correct precedence of &<number>

&<number> is higher precedence than &<match_expr> or &<no_parens_expr>
when run through `Code.string_to_quoted`, so
`matchedExpressionCaptureOperation` needs to add `number` to it's
ordered choice before `noParenthesesExpression` so that `&1 + &2` parses
as `(&1) + (&2)` instead of `&(1 + (&2))`, but `&a + &b` still parses as
`&(a + (&b))`.