SQL / slt coverage for IN lists

[alamb]

Is your feature request related to a problem or challenge?

• part of Further improve performance of IN list evaluation #19241

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.

Describe the solution you'd like

Add comprehensive SQL coverage for the various IN list optimizations as we implement the various specialized implementations

Describe alternatives you've considered

• Add IN list sqllogictest test (and integer type coverage) #23305
• negated / NOT IN null branches
• Float32/Float64 types
• generic ArrayStaticFilter (e.g. Lists, etc)
• dictionary flattening path

Additional context

No response