Fix Oracle GEOM write #16

[rdubois-mel]

Fixes write issue in Oracle (#16)

Reading had been fixed previously, but writing was still impossible.
(The fix includes handling large GEOMs using cLOBs)

Credit to d______n (The bug fix was written by my colleague from the "Métropole Européenne de Lille")

☑ Checklist

• I've compiled and checked the changes with mvn clean verify
• I tested my changes and added relevant example if possible
• I updated documentation if needed
• Each commit has a meaningful subject line and body
• The pull request addresses just the described changes
• I assume that the licenses are respected
• I self-reviewed my own code

𝌡 Proposed changes

Change in how GEOMs are written in Oracle Spatial databases

Fixes:

• [Bug] Plugin compatibility with Oracle is broken #16

Types of changes:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

GIS Transforms concerned:

• Coordinate system operation
• GIS File input
• GIS File output
• Geometry information
• Geoprocessing
• Geospatial Group by
• Spatial relationship and proximity

🏭 How to test the changes?

Just try to write a GEOM in an Oracle Spatial Database 😉