[SEDONA-170] Add ST_AddPoint and ST_RemovePoint to the Flink API

[sekikn]

Did you read the Contributor Guide?

• Yes, I have read Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

• Yes, the URL of the assoicated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-170. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?

• This PR adds ST_AddPoint and ST_RemovePoint to the Flink API.

How was this patch tested?

• Ran mvn clean install locally
• Ran mkdocs serve and checked the generated API document

Did this PR include necessary documentation updates?

• Yes, I am adding a new API. I am using the 1.3.0 in since vX.Y.Z format.

[bchapuis]

@sekikn In my understanding Apache Flink uses Apache Calcite under the hood. Is that right? Would it make sense to implement these spatial functions directly in Calcite? Here are some recent changes made to calcite relevant to this issue:

apache/calcite@2624925
apache/calcite@250d13c

[jiayuasu]

This looks interesting. Does Flink already support ESRI geometry type before your PR? I checked their doc (https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/types/#data-types-in-the-table-api): Geometry is not listed as primitive type.

In addition, some functions such as spatial aggregation might be able to be ported from Calcite to Flink. Some functions such as ST_Subdivide are actually implemented by Sedona committers for Spark. We just simply port them to Flink.

[bchapuis]

I'm not using Flink and I don't know exactly how they use Calcite. Before my PR, calcite used the ESRI geometry API, it now uses JTS and proj4j. I now started working implicit conversion (text => geometry), aggregation function (Accum, Union, etc.), and try to figure out how to implement other special functions such as (ST_Explode). It would be great if we could share some code/implementation (e.g. ST_AddPoint and ST_RemovePoint are currently missing in calcite).