WHERE TRUE AND .... causes wrong pushdowns, causes wrong results

CREATE INDEX ix1 ON default(type);
CREATE PRIMARY INDEX ON default;
EXPLAIN SELECT * FROM default WHERE TRUE AND type = "xyz" LIMIT 2;

Above query uses primary index instead of ix1 also pushes limit to indexer without
pushing spans.

https://github.com/couchbase/query/blob/master/planner/build_scan.go#L84
This condition is true. It should have been false for AND clause.

https://forums.couchbase.com/t/potential-bug-with-and-true-and-limit-couchbase-enterprise-edition-5-5-2-build-3733/18739