Allow setting geometry type explicitly during layer creation, + misc Bugfixes

[Maxxen]

• Adds support for writing TIME/DATE/TIMESTAMP etc columns through GDAL
• Some GDAL drivers will attempt to read from a file without first checking the file type, this broke when trying to read from directories as DuckDB would immediately throw. We now just return 0 bytes read instead, which triggers GDAL to actually inspect the file. This fixes being able to read from the directory path for formats that commonly span multiple files (such as .gdb and .shp), instead of having to find the explicit inner data files.
• You can now pass a geometry type parameter when copying through GDAL to create a geometry layer of a specific type, which is a requirement for some drivers (e.g. OpenFileGDB) as they don't support mixed geometries.
• Fixes a bug where column in filters that get pushed down into GDAL were not being properly quoted in the case that they contain spaces or special characters.

Example:

COPY (SELECT ST_Point(1,2) as geom, 10 as i) TO '__TEST_DIR__/test.gdb' WITH (FORMAT 'GDAL', DRIVER 'OpenFileGDB', GEOMETRY_TYPE 'POINT');

Closes #247
Closes #240
Closes #238
Closes #233

[aborruso]

great PR, thank you

[davidjbrennan]

Hi @Maxxen. I'm using a very recent build (v0.9.3-dev4116) of DuckDB and the issue is still present of a column name, containing spaces, not being properly quoted when the filter gets pushed down to GDAL using st_read against an Excel spreadsheet. When is your fix likely to be included in the main build of DuckDB?

[Maxxen]

Next DuckDB release is scheduled for tuesday!