3D-related functions for GeoSPARQL

[situx]

This pull request defines query functions with a focus on 3D relations as sourced from associated issues:

• maxM, minM: Retrieve the minimum and maximum M coordinates
• azimuth Closes Use Case ONTO15: Azimuth #565
• compactnessRatio Closes Use Case ONTO18: Compactness Ratio #568
• farthestCoordiante Closes Use Case ONTO20: Farthest Coordinate #577
• force2D Closes Use Case ONTO1: Flattening 3D Geometry to 2D #547
• matrixTransform Closes Use Case: DSTL01-TRANSFORMATION-MATRIX #604
• maxDistance and maxMetricDistance Closes Use Case ONTO21: Maximum Distance #578
• minHeight, minMetricHeight, maxHeight, maxMetricHeight Closes Use Case ONTO5: Minimum and Maximum Height #558
• minWidth, minMetricWidth, maxWidth, maxMetricWidth Use Case ONTO4: Minimum and Maximum Width #549
• minDepth, minMetricDepth, maxDepth, maxMetricDepth Use Case ONTO3: Minimum and Maximum Depth #548
• shortestLine Closes Use Case ONTO22: Shortest Line #600
• longestLine Closes Use Case ONTO23: Longest Line #601
• translate Closes Use Case ONTO24: Translate By Vector #602
• translateMult Closes Use Case ONTO10: Multiply Z coordinates #560
• scale Closes Use Case ONOT9: Shift up or down 3D geometry (add to Z coordinates) #559,
• tessellate Closes Use Case ONTO11: Tessellate Geometry #561

I would like to discuss the function signatures and if approved by the group I will finish the pull request by also adding them to the TTL resources.

Questions:

• translation and scaling: How to determine XYZ axis. By CRS definition?
• rotation function: Rotating around an axis... should the axis be identified with a URI or an axis identifier? CRS Ontology?

Proposal: Rearrange requirements for non-sf functions by purpose:

• Geometry Attributes
• Transformation
• More?