Add ST_ClosestPoint (formerly ST_NearestPoints)

This new H2GIS function is related to the old GDMS function as follows:
```mysql
ST_ClosestPoint(geomA, geomB) = ST_NearestPoints(geomB, geomA)
```
It returns the 2D point on `geomA` closest to geomB. Note that the GDMS
function `ST_ProjectTo` is just a special case:
```mysql
ST_ClosestPoint((multi)linestring, point) = ST_ProjectTo(point, (multi)linestring)
```
For this reason, we will not implement `ST_ProjectTo` in H2GIS.

*Note*: If the closest point on geomA is not unique (it is easy to
imagine an example where there are infinitely many, mathematically
speaking), `ST_ClosestPoint` returns the first one it finds when
traversing geomB's coordinates, so the point returned depends on the
ordering of geomB's coordinates.

TODO: Rename `ST_FurthestPoint` -> `ST_FurthestCoordinate`, since this
function returns coordinates and not points.

TODO: Implement `ST_ClosestCoordinate`, which will return the closest
coordinate (rather than the closest point). (By request of @gpetit)

TODO?: Add `ST_3DClosestPoint`? See
        http://www.postgis.org/docs/ST_3DClosestPoint.html
Add a unit test to clarify ST_ClosestPoint

It was ambiguous which point was returned by ST_ClosestPoint when there
were infinitely many closest points. This unit test shows that the point
returned by ST_ClosestPoint depends on the orientations of geometries A
and B. If they have the same orientation, the point returned is the
first point found in A. If they have opposite orientation, the point
returned is the point of A closest to the first point found in B.
Rename ST_FurthestPoint -> ST_FurthestCoordinate

This function returned the furthest coordinate rather than the furthest
point.
Add ST_ClosestCoordinate

This function was not a part of GDMS or PostGIS but was added for
completeness (cf. ST_FurthestCoordinate).

TODO?: Add ST_FurthestPoint? (Not implemented in JTS)