Declare instants, sequences and segments generic over every temporal type

[estebanzimanyi]

meta/type-scope.json declares temporal_instants, temporal_sequences and temporal_segments generic
over Temporal *, as it declares temporal_start_instant and temporal_end_instant, so each keeps the
signature of every temporal type its wrapper declares: instants, sequences and segments over the
20 temporal types. They take a const Temporal * and validate it for being present alone, so no
signal of MEOS states their scope, and the scope their parameter type gives is tint.

Witness: a catalog derived from MobilityDB master 8600f6905a gives temporal_instants the one
signature instants(tint), and temporal_sequences and temporal_segments likewise one each, so a
binding generated from the public accessors reaches instants, sequences and segments over tint
alone.

Measured over MobilityDB master 8600f6905a and the installed headers of a libmeos built from it:
the three accessors keep 20 signatures each, the first argument ranging over the 20 temporal
types; with the @csqlfn tags of the MobilityDB branch fix/array-accessors-call-the-public-api,
no other function keeps a signature of instants, sequences or segments, and the derived catalog
differs from master's in these eight functions alone. The suite passes, 25 tests skipped as on
master, tests/test_typescope.py stating the three over the generated catalog.

Why: the accessors behind instants, sequences and segments are generic, so their scope is stated
where MEOS states none, as the file states every other generic accessor.