[Query Optimizer Improvement] IN statement for timestamp applied as pruning mechanism properly

Right now if we write something like `SELECT * FROM fact WHERE primary_key_id in ('id1', 'id2', 'id3', .....'id10' ) and created_at in (ts1, ts2, ts3, ts4, ... ts10) LIMIT 2000` it is actually running slower than not passing in `created_at in (xxx....)` filter.
But if we convert the `created_at in (xxx) ` into a range filter, it will run faster. Converted query is like below

`SELECT * FROM fact WHERE primary_key_id in ('id1', 'id2', 'id3', .....'id10' ) and created_at <= 1614426347 and created_at >= 1614426293 LIMIT 2000`

No source files, tests, or entry points are named in the issue. Start by reproducing the timestamp IN query and its range-filter equivalent, then trace query-optimizer pruning for timestamp predicates; done means the IN form prunes effectively and does not regress relative to the range form.

Written by the indexing model from the issue text.