Add basic support for HomeWizard v2 API configuration flow

[DCSBL]

Proposed change

This API allows the user to configure the device via the v2 API. This API is now using a authorization step similar to Hue, where the user has to proof the possession by pressing the button on the device. Therefore the config flow has to be adjusted.

To keep this PR a bit concise, I didn't implement reauthorization, extensive error handling and migration. This will be done in follow-up PR's if that is okay.

You can test this with real hardware, ask me via a DM on discord for instructions.

Waits for #135315
Waits for #135778

Next steps:

• Add support for Zeroconf // v2
• Init integration via v2 API (which actually uses the new API)
• Add reconfiguration flow for revoked token (happens when device is reset)
• Add repair for devices that have v2 support but are not v2 configured (missing a token)
• In the very future; WebSocket support for v2

⚠️ Will be merged in to itermediate-homewizard-v2-branch, which will be a collection of v2-support PR's.

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:
  • Inform user that enabling HomeWizard API is not required when using v2 capable API home-assistant.io#36884
  • Add troubleshooting information for the 'authentication' step in HomeWizard home-assistant.io#37035
  • Add HomeWizard Plug-In battery as supported device in the HomeWizard integration home-assistant.io#37036

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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format 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.

To help with the load of incoming pull requests:

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

[DCSBL]

This feels dirty, if you have ideas/examples how to improve this let me know!

[DCSBL]

More information about this flow can be found here: https://api-documentation.homewizard.com/docs/v2/authorization#create-user-and-get-token

[DCSBL]

@joostlek, I think I’ve processed all the feedback and got the docs ready. Do you mind to take a look at this one again?

[frenck]

Thanks, @DCSBL 👍

../Frenck

Comments addressed