Bump aiohue to 2.3.0

[balloob]

Breaking change

Proposed change

Bump aiohue to 2.3.0

home-assistant-libs/aiohue@2.1.0...2.3.0

https://github.com/home-assistant-libs/aiohue/releases/tag/2.2.0
https://github.com/home-assistant-libs/aiohue/releases/tag/2.3.0

Fixes #48286
Fixes #50110

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

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.
• 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.

[probot-home-assistant]

Hey there @frenck, mind taking a look at this pull request as its been labeled with an integration (hue) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[frenck]

Reverted the typing change, as it triggered Pylint (and doesn't attribute to the fix at this point), so decided to remove it.

Tested:

• Current entry still works (after upgrade, selects HTTPS)
• Setting up new integration works (selects HTTPS)
• Manual entry with an invalid address (tries, HTTPS, falls back to HTTP and eventually fails as expected).