Rebuild for python 3.13

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update python313.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by - please use this URL for debugging.}

[conda-forge-webservices]

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.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• No valid build backend found for Python recipe for package aiohttp using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

[dopplershift]

My guess is the test failures is the same as aio-libs/aiohttp#8952, which was only recently fixed in aio-libs/aiohttp#8898. Should be fixed with a new release; might possibly be solved by pinning this version to yarl <=1.9.4?

[ocefpaf]

Should be fixed with a new release; might possibly be solved by pinning this version to yarl <=1.9.4?

If a new release is not far away we can wait. No strong opinions though, just recommending the easiest path.

[xhochy]

The release hasn't happend and a re-run of CI with a newer yarl version also still fails as some things in yarl have reverted but not all (and will not be). Thus, we should actually pin yarl here and repodatapatch the previous builds, too.

[conda-forge-webservices]

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.

[xhochy]

Depends on conda-forge/yarl-feedstock#62