fix: resolve compatibilities for Metabase (#340)

[VWagen1989]

This PR addresses the issues of the compatiblities between MyDuck and Metabase.
The other BI tools are not tested yet. If there still be compatibility issues for them, we should open another PR for them.

Ref #340
Resolve #342

[Copilot]

Copilot reviewed 5 out of 10 changed files in this pull request and generated no comments.

Files not reviewed (5)

• pgserver/connection_data.go: Evaluated as low risk
• pgserver/duck_handler.go: Evaluated as low risk
• pgserver/iter.go: Evaluated as low risk
• catalog/provider.go: Evaluated as low risk
• pgserver/connection_handler.go: Evaluated as low risk

Comments suppressed due to low confidence (3)

pgserver/in_place_handler.go:124

• Ensure that the new InPlaceHandler struct and its methods are covered by tests.

type InPlaceHandler struct {

pgserver/in_place_handler.go:140

• Ensure that the selectionConversions logic is covered by tests, especially the regex patterns and query conversions.

var selectionConversions = []SelectionConversion{

pgserver/in_place_handler.go:374

• Ensure that the updated shouldQueryBeHandledInPlace function is covered by tests, including all its call sites.

func shouldQueryBeHandledInPlace(h *ConnectionHandler, sql *ConvertedStatement) (bool, error) {

[fanyang01]

The failed COPY DATABASE test will be auto-fixed in DuckDB 1.2: duckdb/duckdb#15548

[fanyang01]

Thanks! Look good. It's the first BI tool that we can seamlessly integrate with. Congratulations!