Release all forgotten resources in tests

[webknjaz]

What do these changes do?

Ever since pytest got updated to v6.2, it started emitting resource
warnings under new Pythons 3.8+ which results in a failed status.

This change addresses this issue by properly most of the resources
so they don't even appear and ignoring the rest in cases of race
conditions and other cases that are hard to track down.

Are there changes in behavior for the user?

No.

Related issue number

N/A

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• If you provide code modification, please add yourself to CONTRIBUTORS.txt
  • The format is <Name> <Surname>.
  • Please keep alphabetical order, the file is sorted by names.
• Add a new news fragment into the CHANGES folder
  • name it <issue_id>.<type> for example (588.bugfix)
  • if you don't have an issue_id change it to the pr id after creating the pr
  • ensure type is one of the following:
    • .feature: Signifying a new feature.
    • .bugfix: Signifying a bug fix.
    • .doc: Signifying a documentation improvement.
    • .removal: Signifying a deprecation or removal of public API.
    • .misc: A ticket has been closed, but it is not of interest to users.
  • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

[codecov]

Codecov Report

Merging #5494 (41d7662) into master (1ec360f) will increase coverage by 0.55%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #5494      +/-   ##
==========================================
+ Coverage   96.61%   97.17%   +0.55%     
==========================================
  Files          41       41              
  Lines        8815     8857      +42     
  Branches     1412     1424      +12     
==========================================
+ Hits         8517     8607      +90     
+ Misses        167      133      -34     
+ Partials      131      117      -14     

Flag	Coverage Δ
unit	97.06% <100.00%> (+0.45%)	⬆️

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

Impacted Files	Coverage Δ
aiohttp/web_request.py	95.99% <100.00%> (+0.52%)	⬆️
aiohttp/tracing.py	100.00% <0.00%> (ø)
aiohttp/cookiejar.py	98.78% <0.00%> (+<0.01%)	⬆️
aiohttp/web_response.py	98.21% <0.00%> (+0.22%)	⬆️
aiohttp/client_reqrep.py	97.86% <0.00%> (+0.34%)	⬆️
aiohttp/helpers.py	96.77% <0.00%> (+0.45%)	⬆️
aiohttp/web_protocol.py	86.41% <0.00%> (+0.90%)	⬆️
aiohttp/web.py	99.14% <0.00%> (+1.70%)	⬆️
aiohttp/test_utils.py	99.68% <0.00%> (+1.86%)	⬆️
... and 4 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1ec360f...3c5aa75. Read the comment docs.

[patchback]

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

❌ Failed to cleanly apply 8c82ba1 on top of patchback/backports/3.8/8c82ba11b9e38851d75476d261a1442402cc7592/pr-5494

Backporting merged PR #5494 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 add remote 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.8/8c82ba11b9e38851d75476d261a1442402cc7592/pr-5494 upstream/3.8

4. Now, cherry-pick PR Release all forgotten resources in tests #5494 contents into that branch:

   $ git cherry-pick -x 8c82ba11b9e38851d75476d261a1442402cc7592

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

   $ git cherry-pick -m1 -x 8c82ba11b9e38851d75476d261a1442402cc7592

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Release all forgotten resources in tests #5494 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.8/8c82ba11b9e38851d75476d261a1442402cc7592/pr-5494

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.