AB#84023 - Add 'in' and 'notIn' operator for dashboard filters

[guisoares1]

Description

Implemented two new operators in the query system: ‘in’ and ‘notIn’.
The ‘in’ operator checks if a given value is present in an array.
The ‘notIn’ operator is the opposite of the ‘in’ operator.

Useful links

• Link to ticket
• Frontend

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

• I intercepted the request in the back end that handles the filters (all.ts, line 401) and built a json object for testing purposes.

Screenshots

Result of tests

Base filter test object:

{
  "logic": "and",
  "filters": [
    {
      "logic": "and",
      "filters": [
        {
          "logic": "and",
          "filters": []
        }
      ]
    },
    {
      "logic": "and",
      "filters": [
        {
          "field": "name",
          "operator": "in",
          "value": ["elemento1", "elemento2", "elemento3"]
        }
      ]
    }
  ]
}

Result to "in":

{
  "$and": [
    {
      "$and": [
        {}
      ]
    },
    {
      "$and": [
        {
          "data.name": {
            "$in": [
              "elemento1",
              "elemento2",
              "elemento3"
            ]
          }
        }
      ]
    }
  ]
}

Result to "notin":

{
  "$and": [
    {
      "$and": [
        {}
      ]
    },
    {
      "$and": [
        {
          "data.name": {
            "$nin": [
              "elemento1",
              "elemento2",
              "elemento3"
            ]
          }
        }
      ]
    }
  ]
}

Checklist:

( * == Mandatory )

• * I have set myself as assignee of the pull request
• * My code follows the style guidelines of this project
• * Linting does not generate new warnings
• * I have performed a self-review of my own code
• * I have put the ticket for review, adding the oort-backend team to the list of reviewers
• * I have commented my code, particularly in hard-to-understand areas
• * I have put JSDoc comment in all required places
• * My changes generate no new warnings
• * I have included screenshots describing my changes if relevant
• * I have selected labels in the Pull Request, according to the changes with code brings
• I have made corresponding changes to the documentation ( if required )
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

More explanation

https://www.loom.com/share/05a716d61b9744faaf51fb304c21d1e5?sid=f87cf896-582a-4f76-93ae-8ceed801b145

[MwanPygmay]

@guisoares1 working well for resources, but did not work for reference data, created front-end branch for it, will edit the pr

[AntoineRelief]

@MwanPygmay
is there any reason why this is so different from the solution proposed in the first file?