Add support for AdGuard Home v0.99.0

[frenck]

Breaking Change:

The AdGuard Home integration has been made compatible with AdGuard Home v0.99.0. However, support for lower versions is now limited. Upgrading to AdGuard Home v0.99.0 or newer is advised.

Description:

AdGuard Home introduced some significant API changes (and bugs) in version v0.99.0.
This bump addressed these. However, it would cause an instant drop in support older version.

Release notes: https://github.com/frenck/python-adguardhome/releases/tag/v0.3.0

Related issue (if applicable): fixes #27918

Pull request with documentation for home-assistant.io (if applicable): n/a

Example entry for configuration.yaml (if applicable):

n/a

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• 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.

[pvizeli]

Maybe you can ask API version and show a warning?

[frenck]

Thanks, @pvizeli, good feedback.

• Added logs
• Added feedback/handling in the config flow for manual setup
• Added feedback/handling in the config flow for Hass.io add-ons
• Updated tests.

The spelling error in this screenshot has been fixed.

[cgtobi]

LGTM