Bump async_upnp_client to 0.16.0

[StevenLooman]

Proposed change

Bump async_upnp_client to 0.16.0 from 0.14.3, containing some fixes.

Note that this PR invalidates PR #47885.

Also note that this change to async_upnp_client providers IPv6 support which impacts SSDP-advertisement behavior. Testing this (by others, not being me) should be done.

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)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
  • Asus Rotuer Upnp integration #46822 (preparation for fix)
  • Release 0.1.2-alpha dependency to async-upnp-client breaks integration B5r1oJ0A9G/teufel_raumfeld#7
  • Several in https://github.com/StevenLooman/async_upnp_client
• Link to documentation pull request:
• Additional information, from PR Bump async-upnp-client to 0.15.0 #47885:
  • This PR fixes the dependency issue of the Teufel Raumfeld integration: Release 0.1.2-alpha dependency to async-upnp-client breaks integration B5r1oJ0A9G/teufel_raumfeld#7. Teufel Raumfeld depends on HTTP header support and retention of XML values implemented with release 0.15.0 of async-upnp-client.
  • Changelog release 0.15.0/0.16.0 of async-upnp-client: https://github.com/StevenLooman/async_upnp_client/blob/development/CHANGES.rst
  • Comparing changes release 0.16.0 to 0.14.13: StevenLooman/async_upnp_client@0.14.13...0.15.0

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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[bdraco]

SSDP discovery still working 👍

• H network container
• M network container
• M network os
• Run profile - no increase - looks good. might be able to optimize it a bit:

[bdraco]

Test pass. Thanks!

[StevenLooman]

Wow that was really quick, thanks @bdraco.

Wondering though, is this a profiler graph and how did you generate it?

[bdraco]

Wow that was really quick, thanks @bdraco.

Wondering though, is this a profiler graph and how did you generate it?

I'm using the profiler integration with qcachegrind

https://www.home-assistant.io/integrations/profiler/