Entity Centre: support @TimeOnly semantics

[01es]

Description

Date properties with @TimeOnly semantics are not currently supported as selection criteria. If a property with such semantics is added, (e.g., .addCrit(Timesheet_.startTime()).asRange().time().also()), the resultant query assumes today as the date portion.

• [ ] 1. A query needs to generated where functions hourOf(), minuteOf(), and secondOf() would be used to form an appropriate filtering condition. The conditions for minute and second are only applicable if non-zero values are specified.

  For example, the following selection criterion in application to Timesheet.startTime

  should result in condition:

  .hourOf().prop(Timesheet_.startTime()).ge().val(10).and().hourOf().prop(Timesheet_.startTime()).le().val(16)

• [ ] 2. Mnemonics for @TimeOnly selection criteria should be the same as for numeric properties as Date mnemonics Previous, Current and Next are simply not applicable. Potentially @TimeOnly mnemonics could be of values, but this is outside of the scope for this issue.

Expected outcome

Core support for @TimeOnly semantics as selection criteria.