Resolve all shift/reduce conflicts in Rego parser
4 conflicts, all inherent to Rego's grammar where postfix operators
(call, bracket-ref) are ambiguous with rule/statement boundaries:
- LPAREN/LBRACK after term_expr in rule heads: resolved by giving
the infix_expr->term_expr reduction %prec below_LPAREN
- SEMICOLON after literal_stmt in queries: resolved by giving
the single-statement reduction %prec below_SEMI
- LBRACK after contains_key: resolved by giving the bare
CONTAINS rule %prec below_LPAREN