Update fritzconnection requirement to 0.8.4

[AaronDavidSchneider]

Breaking Change:

Update of requirements

Description:

Using different fritzbox components together leads to problems regarding the version of fritzconnection installed in homeassistant. We encountered this problem, when using our custom component:
https://github.com/mammuth/ha-fritzbox-tools/issues/19

See also #27691 and #27699

**Related issue (if applicable):

**Pull request with documentation for home-assistant.io (if applicable):

Example entry for configuration.yaml (if applicable):

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. (not tested yet)
• There is no commented out code in this PR.
• I have followed the development checklist

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

• Documentation added/updated in home-assistant.io

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

• The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[fabaff]

Using different fritzbox components together leads to problems regarding the version of fritzconnection installed in homeassistant. We encountered this problem, when using our custom component:
mammuth/ha-fritzbox-tools#19

This will not solve the issue mentioned because the release is pinned there to 0.8.2. It will also require that the custom component gets an upgrade.

[AaronDavidSchneider]

Using different fritzbox components together leads to problems regarding the version of fritzconnection installed in homeassistant. We encountered this problem, when using our custom component:
mammuth/ha-fritzbox-tools#19

This will not solve the issue mentioned because the release is pinned there to 0.8.2. It will also require that the custom component gets an upgrade.

Thank you, I created a pull request.

[AaronDavidSchneider]

@fabaff: our custom_component uses now version 0.8.4.