feat: drop Python 3.9 and test on Python 3.10/3.12

[deepyaman]

Description of changes

According to NEP-29, we could have dropped Python 3.9 last month.

• Test on 3.10/3.12 in CI, except for a few exceptions (e.g. Flink).
• Apply pyupgrade rules to remove code for Python<3.10.
• Remove workaround for DuckDB geospatial tests.

Issues closed

N/A

[jcrist]

Overall this looks (mostly) good to me. There are two (kinds) of changes made by pyupgrade that I'd like to revert, but the CI and metadata updates look good to me.

[jcrist]

Provided tests pass, this looks good to me! We should get a review by one other person before merging (@gforsyth?) just to ensure I didn't miss anything around the CI setup.

[deepyaman]

Provided tests pass, this looks good to me! We should get a review by one other person before merging (@gforsyth?) just to ensure I didn't miss anything around the CI setup.

FYI tests have passed; the required nix 3.9 test just won't complete, because it's removed.

[cpcloud]

I'll remove the required nix 3.9 test

[cpcloud]

@jcrist @deepyaman I think historically we made this a breaking change. Should we considering changing that convention?

[jcrist]

I think historically we made this a breaking change. Should we considering changing that convention?

I think that dropping a Python version in a minor release seems fine (it's also pretty common in the ecosystem). Since we've updated the minimum version requirement, even pip's solver won't allow them to install the new release with an older version of python. The "breakage" here isn't something a user should be able to encounter.

[cpcloud]

LGTM.

Can we make this a feature or fix PR?

[deepyaman]

LGTM.

Can we make this a feature or fix PR?

Done! Also rebased.