Add IN list sqllogictest test (and integer type coverage)

[alamb]

Which issue does this PR close?

• Part of Further improve performance of IN list evaluation #19241
• part of SQL / slt coverage for IN lists #23307
• Follow on to Optimize Int8 and Int16 integer IN filters #23299

Rationale for this change

We (mostly @geoffreyclaude ) are in the process of optimizing IN lists with specialized implementations for various different data types.

@kosiew suggested in #23299 (comment) that we add SQL level coverage for the IN list optimizations to both cover the dispatch logic as well as ensure everything works end to end.

One small follow-up idea: it could be useful to add a public-path regression through InListExpr::try_new_from_array, or a SQL-level test, for Int8 and Int16 signed values.

What changes are included in this PR?

1. Add in_list.slt file to specifically target the IN lists
2. Only add test coverage for integer types

note I think we should have significiantly more SLT coverage (list on #23307) but to keep the review small / understandable I plan to do it with several PRs

Are these changes tested?

Only tests

Are there any user-facing changes?

No

[geoffreyclaude]

Very clear and hits quite a few edge cases. Could you just extend the tests to also include longer in lists (eg, 12 elements)?

[alamb]

Very clear and hits quite a few edge cases. Could you just extend the tests to also include longer in lists (eg, 12 elements)?

Done

[alamb]

I also added a note to point out that the IN list is only executed for larger lists (over 4)

[geoffreyclaude]

I also added a note to point out that the IN list is only executed for larger lists (over 4)

We'll have to review that optimization rule once the full IN LIST optims land!

[alamb]

I also added a note to point out that the IN list is only executed for larger lists (over 4)

We'll have to review that optimization rule once the full IN LIST optims land!

Indeed

At some point stuff like PruningPredicate didn't know how to handle IN lists either -- but I believe now that IN LIST is handled quite well at this point across the system