feat(python): Add storage_options in write_parquet

[ion-elgreco]

#9770

You can now pass fsspec kwargs into write_parquet just as in read_parquet.

Example:

import polars as pl

df = pl.from_repr(
"""
┌─────┬─────┬─────┬────────┐
│ a   ┆ b   ┆ c   ┆ column │
│ --- ┆ --- ┆ --- ┆ ---    │
│ i64 ┆ i64 ┆ i64 ┆ str    │
╞═════╪═════╪═════╪════════╡
│ 1   ┆ 2   ┆ 3   ┆ hello  │
│ 2   ┆ 1   ┆ 3   ┆ world  │
│ 1   ┆ 2   ┆ 2   ┆ ...    │
└─────┴─────┴─────┴────────┘
""")

fp = "abfs://polarstest@<storage_account_name>.dfs.core.windows.net/test/new.parquet"
storage_options = {
    "account_key": <KEY>,
}
df.write_parquet(fp, storage_options=storage_options)

pl.read_parquet(fp, storage_options=storage_options)

shape: (3, 4)

a	b	c	column
i64	i64	i64	str
1	2	3	"hello"
2	1	3	"world"
1	2	2	"..."

[ion-elgreco]

@stinodego @cnpryer are there any changes I need to make for this PR to get merged?

[svaningelgem]

Hi @ion-elgreco : I'd love to see the possibility to pass in the path directly, much as it is being done in the read_parquet. After that it's just opened with fsspec.

Additionally: why only parquet, why not the other write_* methods as well?

[ion-elgreco]

Hi @ion-elgreco : I'd love to see the possibility to pass in the path directly, much as it is being done in the read_parquet. After that it's just opened with fsspec.

Additionally: why only parquet, why not the other write_* methods as well?

Was checking write_parquet at that time and that seemed easiest to add. I could add the other ones, but I need to know if I'm on the right track first^^