feat: add Expr.to_dicts()

[NickCrews]

fixes #9185

I hope that the name to_dicts won't lead people to think this returns a dict[column_name, list[values]. I don't think it will. This is why I included the Column.to_list() method in the "See Also" section. I can be more explicit there if you think this is good. I considered the name to_records, but I like to_dicts more. Open ot other ideas.

I'm not sure if we want to sneak this in for 10.0, the implementation doesn't look that hard to review, but the increased API is really what to watch out for here I think.

[ibis-docs-bot]

Docs preview: https://pr-10697-6b0c69969f61a702409f3d5b4aa83a11ebdbe4bd--ibis-quarto.netlify.app

[kszucs]

I don't have a strong preference, but maybe call it to_records()?

[cpcloud]

One of the issues with methods like these (to_list, to_dicts, to_records) is that their API tends to add support for different shapes by stuffing in a bunch of non-mutually exclusive arguments.

Can we a pick a name for this that is both concise and mostly-unambiguously indicates the shape of the dictionary/list-of-dictionaries?

[cpcloud]

Here are my current thoughts:

• to_dicts: implies a sequence because of the pluralization, pigeonholes the output type in perpetuity to literal python dictionaries
• to_records: implies a mapping or something like named tuple (a thing with fields), leaves the individual record type open.

[NickCrews]

I went through the same train of thought as Phillip and that is why I chose to_dicts after considering to_records. Phillip are you saying you are happy with to_dicts or do you see a problem with it?

The two basic shapes I see are Iterable[mapping] (this PR) and Iterable[Iterable] such as an Iterable of tuples or named tuples. Is there another basic shape we might want to support?

I DEFINITELY want different methods for the different shapes. Eg avoid pandas chaos where their to_records() gives you totally different things depending on what you pass to orient. But I'm not sure if I think we need a single method for every concrete type. Eg do we want to_tuples() and to_namedtuples(), or to_rows(record_type=tuple | namedtuple)?
I think I am more of a fan of splitting them into separate methods. One reason is that namedtuples blue the line between being an Iterable and being a mapping.