Inspect TPC-H plans and flag bad ones

[mbasmanova]

PR #581 captured plans for all TPC-H queries. Next step is to examine these plans and flag bad ones for fixing.

CC: @oerling @feilong-liu @MBkkt @pansatadru @pashandor789 @pedroerp @aditi-pandit

[MBkkt]

@mbasmanova

One issue that I noticed, it's not only axiom fault, but a lot of queries have "remaining filter":

Example
q19

-- TableScan[2][table: part, remaining filter: (or(and(between(cast("p_size" as BIGINT),1,15),and(eq("p_brand",Brand#34),in("p_container",{LG CASE, LG BOX, LG PACK, LG PKG}))),or(and(between(cast("p_size" as BIGINT),1,5),and(eq("p_brand",Brand#12),in("p_container",{SM CASE, SM BOX, SM PACK, SM PKG}))),and(between(cast("p_size" as BIGINT),1,10),and(eq("p_brand",Brand#23),in("p_container",{MED BAG, MED BOX, MED PKG, MED PACK})))))), data columns: ROW<p_partkey:BIGINT,p_name:VARCHAR,p_mfgr:VARCHAR,p_brand:VARCHAR,p_type:VARCHAR,p_size:INTEGER,p_container:VARCHAR,p_retailprice:DOUBLE,p_comment:VARCHAR>] -> p_partkey:BIGINT, p_brand:VARCHAR, p_size:INTEGER, p_container:VARCHAR

• Avoid remaining filter for single field: see perf: Improve expr to subfield filters velox#15361
• Avoid remaining filter for multiple field conjunction (or not (A || B) => !A && !B: create separate filter for a and separate filter for b, can be done in velox, but needs to change API/add new API

So algorithm should be following:

1. if filter for single subfield => push-down filter
2. else if filter is negation => demorgan to remove not
3. else if filter is conjunction => check separate filters
4. else if filter is disjunction => remaining