fix: support in in json search

[nityanandagohain]

Fixes #6441

---

Important

Add support for 'IN' and 'NOT_IN' operators in JSON search filters in jsonFilterEnrich() and update tests.

• Behavior:
  • Support for 'IN' and 'NOT_IN' operators in JSON search filters added in jsonFilterEnrich() in enrich_query.go.
  • Determines data type of first element in array for 'IN' and 'NOT_IN' operators.
• Tests:
  • Added test cases for 'IN' and 'NOT_IN' operators in enrich_query_test.go and json_filter_test.go.
  • Updated TestJsonEnrich and TestGetJSONFilter to include new scenarios.

^{This description was created by for e4092f8. It will automatically update as commits are pushed.}

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to e4092f8 in 38 seconds

More details

• Looked at 110 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. pkg/query-service/app/logs/v4/json_filter_test.go:197

• Draft comment:
  The test case for the 'IN' operator in JSON filters is a valid addition and resolves the issue mentioned in the PR.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The PR introduces a new test case for the 'IN' operator in JSON filters, which is a valid addition to resolve the issue mentioned.

Workflow ID: wflow_R7kisGXHKllOPxOb

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[srikanthccv]

Should you cast all the values to the type of the first element? Does it break otherwise if there are different types in the list (assume from API)?