fix: define criterion right operand as any

[ndr-brt]

Description

Define CriterionInput operandRight as any, because it could be an arrays of string or a free form object, e.g.:

{
  "operandLeft": "id",
  "operator": "in",
  "operandRight": ["1", "2"]
}

notes

• separated Criterion from CriterionInput
• minor refactorings

[fdionisi]

What's the issue we are solving here?

[ndr-brt]

whops, forgot to add details 🥲

[fdionisi]

Now I better understand. Thank you, Andrea.

These changes fit the needs, but I'd like to see how we can strongly type the library in the future. Perhaps a developer experience/tech debt issue to open as a follow-up. Would that work?

Nevertheless, great job!

[ndr-brt]

Now I better understand. Thank you, Andrea.

These changes fit the needs, but I'd like to see how we can strongly type the library in the future. Perhaps a developer experience/tech debt issue to open as a follow-up. Would that work?

Nevertheless, great job!

I'm not sure, it depends from what direction we want to follow, as a criterion for a right argument we could theoretically accept every kind of object, so any looks fine to me (in the EDC codebase in java we are using Object).