[feat] improvements to duckDB column type handling

[igorDykhta]

• this PR intends to preserve column types between different types of ingestion into Kepler and DuckDb

Goals:

• timestamps stored as strings from Arrow tables are recognized as timestamps.
• apply extra metadata from table.schema.metadata (geoparquet files).
• DuckDB geometry is automatically casted to WKB, and properly marked with geoarrow extensions.
• DuckDB column types and query result Arrow table types consolidation.
• Apply extra logic only to the last select query.

- geoarrow constants to constants module
- add getSampleForTypeAnalyzeArrow to support and not fail for arrow data
- arrowSchemaToFields accepts extra info from DuckDB table schemas. JSON type gets GEOMETRY_FROM_STRING type, GEOMETRY with geoarrow metadata gets GEOMETRY type, timestamp ...
- fix in validateInputData - check analyzerType only for current field
- fix in validateInputData - support arrow input data

[netlify]

✅ Deploy Preview for kepler-duckdb ready!

Name	Link
🔨 Latest commit	3860fbd
🔍 Latest deploy log	https://app.netlify.com/sites/kepler-duckdb/deploys/67b4aaf40535820008d735f7
😎 Deploy Preview	https://deploy-preview-2970--kepler-duckdb.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.