Some valid filters are not pushed down to parquet scan

[thinkharderdev]

Describe the bug
A clear and concise description of what the bug is.

Certain filter predicates cause an error when building the parquet predicate so the predicate does not get pushed down to the parquet scan. Since the pushdown is currently inexact, the results are still correct but we can potentially lose the performance benefit of pushing the filter down to the scan

To Reproduce
Steps to reproduce the behavior:

Add a filter predicate that uses the same column expression more than once in a single predicate, for example SELECT * FROM table WHERE a = 1 OR a = 2

Expected behavior
A clear and concise description of what you expected to happen.

The predicate a = 1 OR a = 2 should be pushed down to the parquet scan.

Additional context
Add any other context about the problem here.