If this passes the CI than we likely have a gap in test coverage

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.41%. Comparing base (bf14909) to head (2694229).
Report is 3010 commits behind head on master.

✅ All tests successful. No failed tests found.

@@            Coverage Diff             @@
##           master    #9267      +/-   ##
==========================================
+ Coverage   97.79%   98.41%   +0.62%     
==========================================
  Files         108      107       -1     
  Lines       34949    34828     -121     
  Branches     4170     4132      -38     
==========================================
+ Hits        34178    34277      +99     
+ Misses        574      380     -194     
+ Partials      197      171      -26     

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

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

❌ Failed to cleanly apply 947b9c4 on top of patchback/backports/3.10/947b9c43374a2d6a73baab31c5f4bc106d4683ef/pr-9267

Backporting merged PR #9267 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.10/947b9c43374a2d6a73baab31c5f4bc106d4683ef/pr-9267 upstream/3.10

4. Now, cherry-pick PR Fix double unquoting in url dispatcher #9267 contents into that branch:

   $ git cherry-pick -x 947b9c43374a2d6a73baab31c5f4bc106d4683ef

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

   $ git cherry-pick -m1 -x 947b9c43374a2d6a73baab31c5f4bc106d4683ef

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix double unquoting in url dispatcher #9267 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/947b9c43374a2d6a73baab31c5f4bc106d4683ef/pr-9267

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.

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

❌ Failed to cleanly apply 947b9c4 on top of patchback/backports/3.11/947b9c43374a2d6a73baab31c5f4bc106d4683ef/pr-9267

Backporting merged PR #9267 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/947b9c43374a2d6a73baab31c5f4bc106d4683ef/pr-9267 upstream/3.11

4. Now, cherry-pick PR Fix double unquoting in url dispatcher #9267 contents into that branch:

   $ git cherry-pick -x 947b9c43374a2d6a73baab31c5f4bc106d4683ef

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

   $ git cherry-pick -m1 -x 947b9c43374a2d6a73baab31c5f4bc106d4683ef

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix double unquoting in url dispatcher #9267 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/947b9c43374a2d6a73baab31c5f4bc106d4683ef/pr-9267

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.

home-assistant/core#126468

all passing now.

I think we are good to do the stable release