Check the append aggregates on the typed Flink surface

[estebanzimanyi]

GeneratedSqlSurfaceTest.appendAggregatesAnswerWhatMobilityDBAnswersOrderedByTime checks, in a
streaming job and in a batch job of two phases, that appendInstantAgg over temporal integers,
over temporal floats with the interpolation discrete, and with the interpolation linear, a
distance of 1.5 and an interval of one day, over temporal booleans with the interpolation step
and an interval of one day, and appendSequenceAgg over temporal integer sequences answer what
MobilityDB answers over the same values ordered by their start timestamp, the values given out of
that order; and that two values at one timestamp are refused with MobilityDB's error, "The
temporal values have different value at their common timestamp". It is the twin of
MobilitySpark's test.

Witness: with the generator of JMEOS ba1e61c3, before #172, the surface registers neither aggregate, the
77 overloads of appendInstantAgg and appendSequenceAgg left out as stating no combine.

Measured over MobilityDB 3a8e6dba09, the catalog of MEOS-API 4baf11705c and JMEOS main e8c65dc4:
the 34 binding tests pass, 18 of them in GeneratedSqlSurfaceTest, and the 12 benchmark tests, with
0 warnings.

Why: a trajectory built from its instants or its pieces answers on Flink as it does in
PostgreSQL, whatever order Flink hands the rows in.