Relative paths behave differently with spatial extension than with others

Example:

GDB data:
```
wget https://s-media.nyc.gov/agencies/dcp/assets/files/zip/data-tools/bytes/nyc_mappluto_24v1_fgdb.zip -O /tmp/nyc_mappluto_24v1_fgdb.zip
unzip -o /tmp/nyc_mappluto_24v1_fgdb.zip -d ~/data/nyc_mappluto_24v1_fgdb
```

DuckDB usage:
```
SELECT * FROM ST_READ('/Users/me/data/nyc_mappluto_24v1_fgdb/MapPLUTO24v1.gdb')
```

The above works, but with read_csv and others, relative paths are accepted. (Was getting uninformative errors when using `SELECT * FROM ST_READ('~/data/nyc_mappluto_24v1_fgdb/MapPLUTO24v1.gdb')` as I am more used to DuckDB vs spatial duckdb syntax)

Thank you for an awesome extension!! It's leading to this: https://jaanli.github.io/new-york-real-estate/