State the MobilityDB contrib against the MobilityDB 1.4 API

[estebanzimanyi]

The catalog type is MeosType and its accessors are meostype_oid and oid_meostype; span_spgist_get_span takes the query datum and its MEOS type; the span predicates are overlaps_span_span, adjacent_span_span, left_span_span, overleft_span_span, right_span_span and overright_span_span; the span distance is distance_double of distance_span_span in the base type of the key; the bins of a span set and of the time of a temporal value come from spanset_bins and temporal_time_bins; and a temporal geo answers its box with tspatial_to_stbox, its splits with tgeo_split_n_stboxes and tgeo_split_each_n_stboxes, and its tiles with tgeo_space_time_boxes over a geom_in origin. The origin of the time bins is a value of the base type of the span set, a date for a date span set and a timestamptz otherwise, read through the PostgreSQL input function of that type. The duration parameter reaches interval_in through DirectFunctionCall3, which is the arity of a PostgreSQL input function, and a time bin split states that the operator class requires a duration rather than reaching spanset_bins without one. Two spans that share a boundary value are adjacent whatever their bound inclusivity, so an adjacent pair may also overlap and a single entry of a multi-entry key is neither strictly left nor strictly right of the query; the leaf consistent method answers adjacency with the same conservative test the inner one already uses. The header declares the MobilityDB surface the contrib calls, and each translation unit includes the PostgreSQL random-generator header that the installed MEOS internal header needs.