fix: DuckDB initialization when either base prefix is not empty or a non-default project id is used.

[martyngigg]

Summary

A couple of minor fixes related to the DuckDB query tab:

• Fixes failure to load DuckDB assets on a non-empty base path
• Fixes DuckDB attach statement for non-default project ids

DuckDB assets

When the Lakekeeper UI sits on a non-empty base path, e.g. /iceberg/ui, it would fail to load the DuckDB WASM assets as the logic to strip the path components removed the /iceberg part:

These changes pass the configured baseUrlPrefix through to useDuckDB function to allow it to find the assets.

DuckDB attach for non-default project ids

In the case where a non-default project is used then the DuckDB attach statement requires the project id be prefixed to the catalog name.

[martyngigg]

@v-kessler Could I highlight what I think is a small bug in the DuckDB component? I've suggested a fix here but I'm not sure if it's the right approach?