Web API: crit-only properties support

[jhou-pro]

Description

As part of #777 issue it has been added very simplistic ability to use crit-only properties. For crit-only single range-typed properties (Money, Date, BigDecimal, Integer, Long) we use from argument to define the value for crit-only single parameter and leave to as empty (for crit-only multi we use both arguments). For Boolean crit-only single property we use value argument for that purpose, and for String / entity-typed we use like argument. To demonstrate how it looks, lets define groupingProperty entity-typed crit-only single criterion:

{
  ...
  groupingProperty(like: "Month") @skip(if:true) {
    key
  }
  ...
}

Firstly, like title for the argument can be confusing. Then, we should explicitly "skip" the property from result-set. And we also should add some sub-field as the property is entity-typed and is treated as container.

It is very desirable to design specific arguments with good naming for crit-only properties and, probably, auto-skipping of crit-only properties from result-set. For entity-typed crit-only properties the field should be defined as "not-container-typed".

Also, if #1487 is implemented, mnemonics support should be added to crit-only properties too.

Expected outcome

Robust and full support for crit-only criteria for synthetic entities querying in Web API.