remove python 3.13 upper bound

[LucaMarconato]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[LucaMarconato]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[Zethson]

Given you just merged the 3.12+ PR, you might as well set the min version of Python here to 3.12 as well.

[Zethson]

Also, we should be able to remove the dask version pin, right?

[LucaMarconato]

@Zethson not sure when I'll release spatialdata, I'll start with fixing what is already out.

[LucaMarconato]

Also, we should be able to remove the dask version pin, right?

I left the other deps unchanged because it's for the already-released spatialdata. The incoming release will relax some pins. If you need it I can try to prioritize that release as well.

[Zethson]

OK 👍 Then let's just follow this up with a quick PR that relaxes the rest.

Thank you!