`ilike` and `like` precedence seem overly low

The current precedence makes it so you cannot chain it with `&&.` or `||.` without extra parenthesis. It also doesn't fit with the SQL precedence and I'm not aware of any other reasons for the current precedence.

Locate the definitions or entry points for the `ilike` and `like` operators and inspect any existing precedence tests. Reproduce chaining with `&&.` and `||.` both with and without parentheses, then compare the resulting behavior with the intended SQL precedence; done means the operators can be chained naturally without unnecessary parentheses.

Written by the indexing model from the issue text.