fix: support in/not in filters end to end

[ruchamahabal]

Multi-value filters crashed pages in three ways:

• the agent emitted flat ["in", "A", "B"] shapes; normalize them to ["in", ["A", "B"]] at the tool boundary and reject other malformed lists with a corrective message
• getEvaluatedFilters stripped the operator off every [operator, value] filter before fetching, degrading "!=" / "like" to equality and sending in-lists as bare lists ("too many values to unpack"); keep the pair intact and recover legacy flat shapes at fetch time
• the Edit Data Source dialog had no in/not in operators and silently dropped values from malformed filters; add the operators with proper multi-value inputs (ported from @framework/ui's Filter module: picked options for Select, live record search for Link, comma text otherwise) and lossless de/serialization

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge.

The previously reported nested filter evaluation failure is fixed, and no blocking failure remains.

_{Reviews (2): Last reviewed commit: "fix: evaluate filter values in array" | Re-trigger Greptile}