feat: support read_csv for backends with no native support

[jitingxu1]

Description of changes

For backends that lack native read_csv support, pyarrow.csv.read_csv() will be used.

• Read a single file
• Read all files in a directory, something like this: ./directory/*
• Read files matching a glob pattern
• Support cloud storage systems like S3 and GCP

Issues closed

Partially solve #9448

[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.

[jitingxu1]

skip the Trino and impala in tests

@cpcloud request to review

[jitingxu1]

these backends have their own implementation, some of these options still could pass this test, so I skip these backends.

[gforsyth]

Suggested change

	"""Register a CSV file as a table in the current backend.
	This function reads a CSV file and registers it as a table in the current
	backend. Note that for Impala and Trino backends, the performance may be suboptimal.
	Parameters
	----------
	path
	The data source. A string or Path to the CSV file.
	table_name
	An optional name to use for the created table. This defaults to
	a sequentially generated name.
	**kwargs
	Additional keyword arguments passed to the backend loading function.
	Common options are skip_rows, column_names, delimiter, and include_columns.
	More details could be found:
	https://arrow.apache.org/docs/python/generated/pyarrow.csv.ReadOptions.html
	https://arrow.apache.org/docs/python/generated/pyarrow.csv.ParseOptions.html
	https://arrow.apache.org/docs/python/generated/pyarrow.csv.ConvertOptions.html
	"""Register a CSV file as a table in the current backend.
	This function reads a CSV file and registers it as a table in the
	current backend. Note that for the Impala and Trino backends, the
	performance may be suboptimal.
	Parameters
	----------
	path
	The data source. A string or Path to the CSV file.
	table_name
	An optional name to use for the created table. This defaults to a
	sequentially generated name.
	**kwargs
	Additional keyword arguments passed to the PyArrow loading function.
	Common options include:
	- skip_rows
	- column_names
	- delimiter
	- include_columns
	A full list of options can be found on the following pages:
	https://arrow.apache.org/docs/python/generated/pyarrow.csv.ReadOptions.html
	https://arrow.apache.org/docs/python/generated/pyarrow.csv.ParseOptions.html
	https://arrow.apache.org/docs/python/generated/pyarrow.csv.ConvertOptions.html
	::: {.callout-note}
	Options from each of the above reference pages can be passed directly to
	this function, Ibis will handle sorting them into the appropriate
	options buckets.
	:::

[gforsyth]

Suggested change

	Read a single csv file:
	>>> table = con.read_csv("path/to/file.csv")
	Read a single csv file:
	>>> table = con.read_csv("path/to/file.csv")
	Read a single csv file, skipping the first row, with a custom delimiter:
	>>> table = con.read_csv("path/to/file.csv", skip_rows=1, delimiter=";")
	Read a single csv file, but only load the specified columns:
	>>> table = con.read_csv("path/to/file.csv", include_columns=["species", "island"])

[gforsyth]

This seems like an unrelated formatting change

[gforsyth]

Suggested change

	pytest.skip(f"{con.name} implements its own `read_parquet`")
	pytest.skip(f"{con.name} implements its own `read_csv`")

[gforsyth]

Suggested change

	@pytest.mark.never(
	[
	"duckdb",
	"polars",
	"bigquery",
	"clickhouse",
	"datafusion",
	"snowflake",
	"pyspark",
	],
	reason="backend implements its own read_csv",
	)

You can remove this since you are skipping them inside the test body

[gforsyth]

Hm, I think this should probably be a temp table or a memtable, because none of our other read_* functions create a persistent object

[gforsyth]

memtable is probably a good option

[jitingxu1]

ah, saw your comments, please ignore the above request.