Bump aiohttp to 3.8.4

[bdraco]

Proposed change

changelog: aio-libs/aiohttp@v3.8.1...v3.8.4

Has aio-libs/aiohttp#7180 which is the fix we have been waiting for

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[Kane610]

Awesome 🎉

[bdraco]

thanks

[balloob]

This release of aiohttp still adopts the new behavior that view handlers now no longer get cancelled if the client leaves.

See my comment here

[balloob]

We need aiohttp 3.9 so we can use aio-libs/aiohttp#7056 which gives us the old behavior.

[balloob]

So the new behavior means we don't cancelled the handler but instead rely on errors being raised when we send data to the client. This was broken in 3.8.3 but now works thanks to the fix by bdraco in 3.8.4 (previously we would just run out of memory).

However, this new behavior means all view handlers are now behaving differently than before, and we haven't verified this (and need to verify this for all views? 😱).

[balloob]

For more about the differences between the two, see https://github.com/aio-libs/aiohttp/blob/master/docs/web_advanced.rst#web-handler-cancellation