WKT Reader Update

[pramsey]

Correctly handle Z/M tags, throw errors or coerce dimensionality per the existing behaviour. Match up the MULTIPOINT behaviour to the other behaviour if coercing. Enforce dimensionality through the *whole* object based on the first found source.

For example, a MULTILINESTRING((1 1, 0 0), (1 1 1, 0 0)) should be 2d, because first coordinate was 2D. Currently enforcement is only per-coordinate sequence, so mixed polygon rings, etc, are possible.

• If Z/M tag, that sets the dimensionality for all subsequent components.
• Otherwise first encountered coordinate sets dimensionality.
• For empties, dimensionality is 2D, unless Z/M tagged.

May require some synchronization with WKBReader and WKTWriter.

[robe]

Retargeting in prep for GEOS 3.10.0 release

[dbaston]

Forcing of consistent dimensionality in main with f460e4e5f4b16bc6ae3a4568624366aeae79074d/git Handling of Z/M flags in main with a7dbef87e85cdae8fb5930724a9130d2de90140d/git