ATLAS-5053: Add recursive validation in Basic Search API to fix regression issue

[aditya-gupta36]

What changes were proposed in this pull request?

• Initially under basic and classification search, only basic [Add filter] option on UI, validation was done. Also, for [Add Group FIlter]option on UI it was throwing exception and errors.
• So in this PR we have fixed that issue and we have handled filter search validation for both basic and complex filter groups.
• Group FIlter - it recursively calls Filter SearchParameters. eg: In FilterCriteria class we have List criterion, so entityFilters attribute in SearchParametrs class recursively calls criterion in itself multiple times.
• Apart have added TC to test negative scenarios for quick search and basic search

Conclusion:

"entityFilters": {

"condition": "AND",
"criterion": [
  {
    "attributeName": "__classificationNames",
    "operator": "eq",
    "attributeValue": "GameCatA"
  },
  {
    "condition": "AND",
    "criterion": [
      {
        "attributeName": "year_held",
        "operator": "eq",
        "attributeValue": "2006"
      }
    ]
  }
]

},
"tagFilters": null,
"attributes": [
"__classificationNames",
"__typeName",
"year_held"
],
"limit": 25,
"offset": 0,
"typeName": "tournament",
"classification": null,
"termName": null
}

• As one can see, inside entity filter, we have criterion which in itself has condition and criterion i.e following nested pattern[recursively filtered], si in such case it gives:
  {
  "errorCode": "ATLAS-400-00-103",
  "errorMessage": "Invalid operator specified for attribute: null"
  }

So we have fixed this Complex filter validation[i.e. Add Filter Group Option]. Earlier it was only able to handle basic filter[i.e. normal Add Filter Option]

How was this patch tested?

• Curl Request
• Postman Request
• UI testing
• PC: https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1908/
• CI Build

[pareshddevalia]

LGTM

[pareshddevalia]

LGTM