refactor: remove junctions from query engine API [DHIS2-18041]

[jbee]

Summary

Fixes special filters that would require junctions by moving their composition into the query engine.

While this refactoring removes nested junctions from the query engine API this does not remove a web API feature. Nested junctions were only used in a few special programmatic cases to build more sophisticated filters. Within the Query all filters are now just one Restriction. Sophisticated ones are expanded first within the engine making it unnecessary to model junctions on the Query or Restriction level.

To distinguish Restrictions that are simple from those that need expanding the isVirtual() method got added encoding the few conditions where this is needed.

Simplifications

• removed Criteria, Criterion, Disjunction and Conjunction as all filters are now simple Restrictions
• aliases are no longer in Query but extracted from the Restriction in the JPA query engine when needed
• Typed got replaced by simply using List.of
• Operator.collectionArgs was replaced with using Operator.args instead (there never was a need for another field as only in/not-in operator would use it and they always would only have one list of args that could use args as all other operators)
• QueryPlanner.planQuery with persistedOnly got removed (this was never necessary as Query instances passed to a QueryEngine should always be already planned as they should come from within the QueryService and never be passed to the engine directly)

Corrections

• DefaultJpaQueryParser got renamed to DefaultQueryParser (wasn't specific to JPA in any way)
• QueryEngine generic got removed (it was wrongly made generic when it was not)
• the generic on Operator got changed from <T extends Comparable<? super T>> to <T extends Comparable<T>> (was too unspecific which forced some casts that now can be avoided)

Cleanup

• QueryPath got moved into the schema module and is not computed by the SchemaService (as it really as an extension on Schema and Property that is only used for Query)
• QueryService.query with ResultTransformer got removed (was unused)
• Operator.getHibernateCriterion got removed (was unused)

[sonarqubecloud]

Quality Gate failed

Failed conditions
9 New issues
9 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

To fix the problem, we need to remove the unused parameter Schema schema from the method getDisjunctionsFromCustomMentions. This involves:

1. Removing the parameter from the method signature.
2. Updating any calls to this method to remove the corresponding argument.

This change will simplify the method and its usage without altering its functionality.