fix: issues on WHERE search filter

[techchintan]

Close: Point 3: - Filter - #2353 (comment)
Except for Subpoint - 4 & 6

[palashgdev]

small change... though working fine from functionality perspective

[srikanthccv]

@techchintan please incorporate the changes from this commit b91a13e.

And I noticed the value of the query params is incorrect for the /attribute_values API. Here is what each of them means. This was working earlier.

• aggregateOperator: aggregation operator selected from the list of aggregations supported for each signal.
• dataSource: one of the data sources selected from logs, traces, and metrics.
• aggregateAttribute: aggregation attribute key selected
• attributeKey: The key from the where clause the user has typed. (where keys are fetched from /attribute_keys API)
• tagType: tag type of the key from the where clause the user has typed. (/attribute_keys would have also provided the tag type, that should be used here, null in case of a custom key)
• filterAttributeKeyDataType: data type of the key from the where clause user has typed. (/attribute_keys would have also provided the data type, that should be used here, null in case of a custom key)
• searchText: search text for the value

[srikanthccv]

I do not think the first point is addressed probably related to incorrect query param. The key-op-value flow is not starting unless the aggregate attribute is chosen.

[palashgdev]

will be taking the feedback in another as functionality is working fine