Add additional conditional support to KeywordList filter

[laurakwhit]

Description & motivation 💭

Adds support for Equal to, Not equal to, Is null and Is not null to KeywordList attributes in the filter search.

Screenshots (if applicable) 📸

Before	After

Design Considerations 🎨

Testing 🧪

How was this tested 👻

• Manual testing
• E2E tests added
• Unit tests added

Steps for others to test: 🚶🏽‍♂️🚶🏽‍♀️

• Add a KeywordList custom search attribute (e.g. temporal operator search-attribute create --namespace default --name CustomKeywordListField --type KeywordList)
• Run a workflow with the custom search attribute set (e.g. this one).

---

• Go to the Workflows list view
  • Select Filter > CustomKeywordListField > select In > enter multiple values
    • Verify searching works as expected
  • Select the filter that was created
    • Verify editing the filter works as expected (including changing the conditional)
  • Toggle View Search Input
    • Verify filters show up as expected
  • Refresh the page
    • Verify filters still show up and work as expected

Checklists

Draft Checklist

Merge Checklist

Issue(s) closed

DT-2635

Docs

Any docs updates needed?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
holocene	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 27, 2024 9:24pm

[Alex-Tideman]

What are the uses of the conditionals that aren't "In"? Like is "Equal to" checking the exact list? "Dog, Cat, Bird" Equal to "Dog, Cat, Bird"?

[laurakwhit]

What are the uses of the conditionals that aren't "In"? Like is "Equal to" checking the exact list? "Dog, Cat, Bird" Equal to "Dog, Cat, Bird"?

@Alex-Tideman say a workflow has a CustomKeywordListField with the values keywordA and keywordB. Checking for CustomKeywordListField = keywordA or CustomKeywordListField = keywordB would return the workflow, checking forCustomKeywordListField = keywordC would not. Checking for CustomKeywordListField IN ("keywordA", "keywordB", "keywordC") would also return the workflow even though keywordC is not a defined value for the workflow.

Not sure on usefulness of having both options (CustomKeywordListField = keywordA and CustomKeywordListField In ("keywordA") are essentially the same), but I figure if it's possible to have in the search input we should support it in the filter search.