fix(duckdb): ensure that duckdb columns argument to read_csv accepts duckdb syntax not ibis syntax

[cpcloud]

Fixes an issue where the input strings in the columns (and types) argument to read_csv assumed the input type strings are ibis types, whereas they are actually DuckDB types. Closes #10695.

BREAKING CHANGE: The duckdb backend's read_csv method accepts only DuckDB types for the values components of the columns and types dictionary arguments. You may need need to adjust existing code. For example, the string "float64" should be replaced with the string "double".

[github-actions]

ACTION NEEDED

Ibis follows the Conventional Commits specification for release automation.

The PR title and description are used as the merge commit message.

Please update your PR title and description to match the specification.

[cpcloud]

Apparently, this was intended to support ibis types in the mapping, so the only way I can see to address the issue without breaking existing code is to allow integer in the ibis type parser (the meaning would correspond to duckdb's bigint though).

cc @amoeba

[cpcloud]

I think this is probably better to break for 10.0 and use the behavior that's in this PR, which is that read_csv's columns and types argument for duckdb are in the lingo of DuckDB.

That is, the types are spelled the way duckdb spells them, not the way Ibis spells them.

[amoeba]

That is, the types are spelled the way duckdb spells them, not the way Ibis spells them.

I think this changes matches the behavior I'd expect so 👍 here.