Fix type ignore in SSLContext creation connector test

[bdraco]

Fixes the typing in test_ssl_context_creation_raises. This is not a runtime change.

#8672 (comment)

[Dreamsorcerer]

With a little tweak to the pytest parametrize API that could probably be caught as a type error in the function signature/decorator... 🤔️

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.98%. Comparing base (c3219bf) to head (424fc07).
Report is 821 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #8676   +/-   ##
=======================================
  Coverage   97.98%   97.98%           
=======================================
  Files         107      107           
  Lines       33825    33825           
  Branches     3969     3969           
=======================================
  Hits        33143    33143           
  Misses        505      505           
  Partials      177      177           

Flag	Coverage Δ
CI-GHA	97.88% <100.00%> (ø)
OS-Linux	97.54% <100.00%> (ø)
OS-Windows	95.92% <100.00%> (ø)
OS-macOS	97.21% <100.00%> (ø)
Py-3.10.11	97.35% <100.00%> (ø)
Py-3.10.14	97.28% <100.00%> (ø)
Py-3.11.9	97.51% <100.00%> (ø)
Py-3.12.4	97.63% <100.00%> (ø)
Py-3.8.10	95.56% <100.00%> (ø)
Py-3.8.18	97.07% <100.00%> (ø)
Py-3.9.13	97.22% <100.00%> (ø)
Py-3.9.19	97.16% <100.00%> (ø)
Py-pypy7.3.16	96.75% <100.00%> (ø)
VM-macos	97.21% <100.00%> (ø)
VM-ubuntu	97.54% <100.00%> (ø)
VM-windows	95.92% <100.00%> (ø)

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.10: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 2915102 on top of patchback/backports/3.10/29151021f957a524f612e9effc20ede8538195ab/pr-8676

Backporting merged PR #8676 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/29151021f957a524f612e9effc20ede8538195ab/pr-8676 upstream/3.10

4. Now, cherry-pick PR Fix type ignore in SSLContext creation connector test #8676 contents into that branch:

   $ git cherry-pick -x 29151021f957a524f612e9effc20ede8538195ab

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

   $ git cherry-pick -m1 -x 29151021f957a524f612e9effc20ede8538195ab

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix type ignore in SSLContext creation connector test #8676 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/29151021f957a524f612e9effc20ede8538195ab/pr-8676

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.11: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 2915102 on top of patchback/backports/3.11/29151021f957a524f612e9effc20ede8538195ab/pr-8676

Backporting merged PR #8676 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/29151021f957a524f612e9effc20ede8538195ab/pr-8676 upstream/3.11

4. Now, cherry-pick PR Fix type ignore in SSLContext creation connector test #8676 contents into that branch:

   $ git cherry-pick -x 29151021f957a524f612e9effc20ede8538195ab

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

   $ git cherry-pick -m1 -x 29151021f957a524f612e9effc20ede8538195ab

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix type ignore in SSLContext creation connector test #8676 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/29151021f957a524f612e9effc20ede8538195ab/pr-8676

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.