Carry the full per-type SQL name family in sqlSignatures

[estebanzimanyi]

What

A base-type-generic MEOS C function is exposed by MobilityDB as a per-type name family. tintInst, tbigintInst, …, ttextInst are 15 distinct CREATE FUNCTIONs all backed by the one wrapper Temporal_to_tinstant; the same holds for the sequence / sequence-set constructors, the _in/_out/_recv/_send and From{Binary,HexWKB,MFJSON} I/O families, the value accessors, and the transform families.

The single @sqlfn doxygen tag names only one representative of each family, so sqlSignatures carries just that name's overload (e.g. temporal_to_tinstant → only tintInst(tint)). Every binding therefore generates one type and hand-writes the other 14.

Change

attach_sqlfn_map keeps every CREATE FUNCTION overload the wrapper backs and stamps each entry with its own sqlName when the wrapper backs more than one distinct name. Single-name wrappers stay {args, ret} unchanged, so the common case is a no-op.

A binding registers each overload by sig.get("sqlName", f["sqlfn"]) — its own SQL name — instead of hand-writing the non-representative types.

Effect on the catalog

• 241 functions gain their full name family; none lose signatures; the ~2060 single-name functions are byte-identical.
• temporal_to_tinstant 1→15, tsequence_make 1→17, set_in/set_out 1→16, span I/O 0→5, and alias pairs are surfaced (insert/update, atValue/atValues, contains/set_contains, minDistance/nearestApproachDistance).
• sqlArity/sqlReturnTypeAll already span the whole wrapper, so sqlSignatures is now consistent with them.