Finish backporting aiohttp 3.10 bump

[gerrod3]

Bumping this req broke Pulp, but only when using the downloader outside of a coroutine, which some plugins do (pulp_container).

(from commit 3b0d218)

[gerrod3]

Side note, we will probably have problems with this again when we upgrade past python 3.12, as it will most likely become an error one day: https://docs.python.org/3.11/library/asyncio-eventloop.html#asyncio.get_event_loop

[patchback]

Backport to 3.22: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.22/386c0b99f2baa9f871c9d0a0be44c2be53581746/pr-6007

Backported as #6008

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.39: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.39/386c0b99f2baa9f871c9d0a0be44c2be53581746/pr-6007

Backported as #6009

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.28: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.28/386c0b99f2baa9f871c9d0a0be44c2be53581746/pr-6007

Backported as #6010

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[gerrod3]

Uggh, seems like we have an inconsistent test on the azure runner for 3.49. Seems to fail on the retry-with-bad-response test. The fixture seems to be giving an error. Not sure where to start with this one.

[ggainey]

Uggh, seems like we have an inconsistent test on the azure runner for 3.49. Seems to fail on the retry-with-bad-response test. The fixture seems to be giving an error. Not sure where to start with this one.

FWIW, we've been seing a number of inconsistent tests in the nightlies, that "work fine on restart". hard to pin down exactly what is going on - esp when sometimes, it's clearly "github hiccupped/timed-out/etc"