Geo cord polygon query

[104H]

Allows the user to define the query polygon in any arbitrary coordinate system along with a WKT string of the coordinate system.

The polygon is then transposed from the query-defined system to the system followed by the project.

[jarkenau]

@Mark-Niemeyer what should we do with this? Close PR for now and create an issue?

[mmeijerdfki]

As a follow up:
This PR enables querying in the various spatial reference systems supported by PROJ.

First the polygon from the query is transformed into the projects geodetic spatial coordinate system, if needed.
After that the polygon is transformed into the projects map frame to calculate the spatial relevancy of the stored objects.

Changelog:

• build and install a newer version of PROJ from source
• new property for the flatbuffers query crsString with valid values of codes from https://spatialreference.org/, "map" or "project"
  • if crsString == "map" no transforms will be done and it is assumed that the query is done spatially in the map frame and the query will be executed in the map frame
  • if crsString == "project" only the transform to topocentric will be done, the query will be done in the projects spatial reference system, the query will be executed in the projects spatial reference system
  • if crsString == "<other spatial reference code>" the polygon will be transformed to the projects spatial reference system first and then projected to topocentric
• removed the inMapFrame flag from the query as this is now baked into crsString
• added 3 new tests to check the transformations behavior
• added and updated docs to reflect these additions and changes

Note:
The docker containers have to be rebuild on this branch to pass the tests.