feat: improve LiteralGuarantee for the case like (a=1 AND b=1) OR (a=2 AND b=3)

[haohuaijin]

Which issue does this PR close?

• Closes Bloom filters are unused for certain where clause patterns (improve LiteralGuarantee) #16697

Rationale for this change

improve LiteralGuarantee to handle the case like
(a=1 AND b=1) OR (a=2 AND b=3) or (a IN ("foo", "bar") AND b = 5) OR (a IN ("bar") AND b=6)

What changes are included in this PR?

add the logical to extract (a=1 AND b=1) OR (a=2 AND b=3) to in_guarantee("a", [1, 2]), in_guarantee("b", [1, 3]);

1. splits each disjunction into its constituent conjunctions and filters for equality operations
2. the find_common_columns function that identifies columns present in all termsets
3. iterates through common columns and builds guarantees

Are these changes tested?

yes, add some test case

Are there any user-facing changes?

[haohuaijin]

cc @debajyoti-truefoundry @alamb

[alamb]

Thanks @haohuaijin -- this looks like a great start to me

I think we need a few more tests to show it doesn't incorrectly pick up literal guarantees for NOT IN / != terms, but otherwise I think it is good

[haohuaijin]

Thanks fo you reviews @alamb , i address you comment in 89dc6be

[alamb]

I am sorry @haohuaijin -- I will review this more carefully soon. I just need to sit down and think through the details to make sure it doesn't have any correctness problems

[alamb]

Thank you @haohuaijin -- I reviewed the code and tests carefully and I think this PR looks good to me.

It is a very nice improvement

[haohuaijin]

Thanks for you reviews @alamb