Fix DuckDB DELETE/UPDATE on view-backed tables

[sgrebnov]

Fixes Binder Error: Can only delete from base table! when running DELETE or UPDATE against a DuckDB-accelerated table that was created via overwrite mode.

After an InsertOp::Overwrite, DuckDB exposes data through a view over an internal _data* table. The delete_from implementations used the table definition name directly, which resolves to the view — DuckDB rejects DML on views.

Changes:

1. Add TableDefinition::resolve_dml_table_name() that resolves to the underlying __data_* table when one exists, otherwise returns the base table name (reuses existing list_internal_tables logic)
2. Update DuckDBDeletionSink and DuckDBUpdateSink to resolve the actual table name at execution time
3. Add 3 regression tests: filtered delete, delete-all, and filtered update on view-backed tables