State trgeometry as a reference geometry and a temporal pose in the type registry

[estebanzimanyi]

The temporal role of the type registry names every temporal type whose instants store a value of
the base, the inverse of temptype_basetype in MEOS_RELTYPE_CATALOG: the instants of tgeompoint and
tgeometry store a geometry, and those of tpose and trgeometry a pose. A trgeometry is not
Temporal: it is the concatenation of a reference geometry and a temporal pose, each instant
storing the pose that places the geometry, so its value at an instant is a geometry while getValue
reads the stored pose. The module documentation, the comment beside the inversion and the
invariants of docs/cross-repo-handoff.md state the role and the type this way; the registry and
its consumers, the JMEOS object layer typing getValue over trgeometry as a pose among them, are
unchanged.

Witness: tests/test_typerelations.py passes its 7 tests over MobilityDB master f9c15d092a, the
one reading the live catalog included.