[BUG] read_vortex cannot read Vortex files over HTTP/S3 via httpfs

[iceboundrock]

Overview

The vortex extension fails to read .vortex files stored on an HTTP server or S3 bucket, even though the httpfs extension is loaded. By contrast, read_parquet() works fine on the same remote server.

Using read_vortex('http://.../file.vortex') results in:

Binder Error:
No files matched the glob
Backtrace:
disabled backtrace

Environment

•	Hardware: Apple M1 MacBook Pro
•	OS: macOS 14.6 (Darwin 24.6.0, ARM64)
•	DuckDB version: 1.4.3 (installed via `brew`)

Steps to Reproduce

1. create/find a paqruet file and a vortex file
2. start a simple python HTTP server with python3 -m http.server 8800 command
3. use official duckdb CLI and extensions to query the files

$ duckdb
DuckDB v1.4.3 (Andium) d1dc88f950
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
D load vortex;
D load parquet;
D select count(*) as c from read_parquet('http://localhost:8800/y.parquet');
┌────────────────┐
│       c        │
│     int64      │
├────────────────┤
│    2964624     │
│ (2.96 million) │
└────────────────┘
D select count(*) as c from read_vortex('http://localhost:8800/y.vortex');
Binder Error:
No files matched the glob
Backtrace:
disabled backtrace

LINE 1: select count(*) as c from read_vortex('http://localhost:8800/y.vortex');
                                  ^

Expected Behavior

read_vortex() should be able to read Vortex files from remote locations supported by httpfs, including HTTP/S URLs and S3 paths, just like read_parquet().