dask 2025.1.0 compatibility

[TomAugspurger]

This updates dask-geopandas to be compatible with the next release of
dask, which moves dask-expr into dask.dataframe.

I've dropped support for all older versions of dask. Only new versions,
based on dask-expr / with query planning, are supported.

dask currently supports Python>=3.10, so I've bumped that requirement as well.

Closes #324

[TomAugspurger]

OK, the upstream-dev tests passed at https://github.com/geopandas/dask-geopandas/actions/runs/12734777705/job/35492743562?pr=324. The rest are failing because that's using a new dask.dataframe.api module that's present on main but not yet released. IMO, we can plan to release dask-geopandas the same day as dask 2025.1.0, and maintain compatibility without a ton of compatibility code.

[martinfleis]

I am fine with the approach. I suppose we can merge this and cut a release, given task 2025.1 was released yesterday? Might be worth getting #322 in as well prior the release.

[TomAugspurger]

Just merged conda-forge/dask-core-feedstock#229. Will make a PR for conda-forge/dask-feedstock next (conda-forge/dask-feedstock#284).

[martinfleis]

Thanks Tom!

[TomAugspurger]

Removed the compatibility handling around use_nullable_dtypes. We just do the same as upstream dask now.

Planning to merge this and #322 before cutting a release.

[TomAugspurger]

I'm not sure why the GitHub Action had a failure at https://github.com/geopandas/dask-geopandas/actions/runs/12857203343/job/35844805603, but version 0.4.3 was uploaded to PyPI: https://pypi.org/project/dask-geopandas/0.4.3/