Expose table scan progress to DuckDB

[myrrc]

Add table_scan_progress in duckdb's table function vtable. Return sum of read
(exported) chunks' length divided by sum of all chunks' length.

Unrelated changes:

• panic in duckdb-bench if no output formats were provided
• add a note how to set up duckdb-vortex's full testing with vortex-duckdb.

Testing:

• Generate .vortex files: cargo run --bin duckdb-bench -- tpch -i1 --opt scale-factor=10.0 --formats vortex

2. Build duckdb vortex extension from this PR
3. Verify these queries show progress bar

PRAGMA enable_progress_bar;
SET progress_bar_time = 10;
select * from read_vortex("/path/to/vortex/vortex-bench/data/tpch/10.0/vortex-file-compressed/l*.vortex");

[myrrc]

But yeah maybe it's best to keep the APIs aligned.

I believe if we can use one pointer we shouldn't pass three, and as we reimplement table function's vtable anyway, we can cut some corners, but this is minor, so I've reverted the code.

[gatesn]

This is wrong right? The variable is called bytes_read, but we're adding the row count of the chunk.

We're also adding this after pulling the chunk? So presumably the progress just hovers around or just below 100% the entire time?

I think we need to figure out a better measure of progress using the Scan API after #6652