colexec: problems with AND and OR operators

[yuzefovich]

Currently, we have some issues with AND and OR logical operators when they are used as projecitons:

• AND doesn't follow the short-circuiting approach

statement ok
DROP TABLE IF EXISTS t; CREATE TABLE t (k INT PRIMARY KEY, a INT, b INT)

statement ok
INSERT INTO t VALUES (1, NULL, NULL), (2, NULL, 1), (3, 1, NULL), (4, 2, 0), (5, 3, 3)

# Test AND short-circuiting projection logic (check that the right side is not
# evaluated when the left side is false).
query B
SELECT a <> 2 AND 3 / b = 1 FROM t ORDER BY k
----
NULL
false
NULL
false
true

• OR expression is replaced by CASE operator that is not fully equivalent to the desired expression when nulls are present.