Bump yarl to 1.18.3

[bdraco]

Bumping ahead of dependabot to get a new benchmark baseline as cache hit is a lot more likely with this version.

[codspeed-hq]

CodSpeed Performance Report

Merging #10078 will not alter performance

_{Comparing bump_yarl1183 (84977ba) with master (1fa237f)}

Summary

✅ 44 untouched benchmarks

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.76%. Comparing base (1fa237f) to head (84977ba).
Report is 1 commits behind head on master.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #10078   +/-   ##
=======================================
  Coverage   98.76%   98.76%           
=======================================
  Files         121      121           
  Lines       36860    36860           
  Branches     4396     4396           
=======================================
  Hits        36403    36403           
  Misses        311      311           
  Partials      146      146           

Flag	Coverage Δ
CI-GHA	98.64% <ø> (ø)
OS-Linux	98.33% <ø> (ø)
OS-Windows	96.18% <ø> (ø)
OS-macOS	97.44% <ø> (+<0.01%)	⬆️
Py-3.10.11	97.29% <ø> (ø)
Py-3.10.15	97.88% <ø> (ø)
Py-3.11.10	97.86% <ø> (-0.01%)	⬇️
Py-3.11.9	97.35% <ø> (+<0.01%)	⬆️
Py-3.12.7	98.39% <ø> (-0.01%)	⬇️
Py-3.13.0	98.37% <ø> (-0.02%)	⬇️
Py-3.9.13	97.20% <ø> (ø)
Py-3.9.20	97.74% <ø> (-0.05%)	⬇️
Py-pypy7.3.16	97.35% <ø> (-0.01%)	⬇️
VM-macos	97.44% <ø> (+<0.01%)	⬆️
VM-ubuntu	98.33% <ø> (ø)
VM-windows	96.18% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[patchback]

Backport to 3.11: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 0d6a83e on top of patchback/backports/3.11/0d6a83e4e6ee9beb99056daa48283d82a7355ee0/pr-10078

Backporting merged PR #10078 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.11/0d6a83e4e6ee9beb99056daa48283d82a7355ee0/pr-10078 upstream/3.11

4. Now, cherry-pick PR Bump yarl to 1.18.3 #10078 contents into that branch:

   $ git cherry-pick -x 0d6a83e4e6ee9beb99056daa48283d82a7355ee0

   If it'll yell at you with something like fatal: Commit 0d6a83e4e6ee9beb99056daa48283d82a7355ee0 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 0d6a83e4e6ee9beb99056daa48283d82a7355ee0

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Bump yarl to 1.18.3 #10078 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/0d6a83e4e6ee9beb99056daa48283d82a7355ee0/pr-10078

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

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

[patchback]

Backport to 3.12: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 0d6a83e on top of patchback/backports/3.12/0d6a83e4e6ee9beb99056daa48283d82a7355ee0/pr-10078

Backporting merged PR #10078 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.12/0d6a83e4e6ee9beb99056daa48283d82a7355ee0/pr-10078 upstream/3.12

4. Now, cherry-pick PR Bump yarl to 1.18.3 #10078 contents into that branch:

   $ git cherry-pick -x 0d6a83e4e6ee9beb99056daa48283d82a7355ee0

   If it'll yell at you with something like fatal: Commit 0d6a83e4e6ee9beb99056daa48283d82a7355ee0 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 0d6a83e4e6ee9beb99056daa48283d82a7355ee0

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Bump yarl to 1.18.3 #10078 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.12/0d6a83e4e6ee9beb99056daa48283d82a7355ee0/pr-10078

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

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