Bump homeassistant to 2026.2.0 for pycares 5 compatibility

[renovate]

What

Renovate bumped pycares from >=4.9.0,<5.0.0 to >=5.0.1,<5.1.0. pycares 5.0 removed the ares_query_* result classes that aiodns < 4.0 references at import time — and since aiohttp's DNS resolver only catches ImportError, the AttributeError escapes and any import aiohttp crashes. Every test imports homeassistant → aiohttp, so the whole suite errored at collection.

The incompatibility is not fixable repo-side on the old HA: homeassistant==2025.10.2 exact-pins aiodns==3.5.0. The fix is to bump the dev/CI Home Assistant to 2026.2.0, the first release that pins aiodns>=4.0.0 (aiodns 4.x drops the annotation entirely).

Changes

• requirements.txt:
  • homeassistant==2025.10.2 → homeassistant==2026.2.0 (pins aiodns==4.0.0, aiohttp==3.13.3)
  • pycares>=4.9.0,<5.0.0 → pycares>=5.0.1,<5.1.0 (the renovate bump, now viable)
  • Updated the explanatory comment

Validation

• Full test suite: 64 passed with homeassistant 2026.2.0 + aiodns 4.0.0 + pycares 5.0.1 (CI-equivalent fresh venv, Python 3.13)
• ruff check . clean; scripts/typecheck (mypy) clean — 12 source files

Notes

• This is a dev/CI-only dependency pin. hacs.json / AGENTS.md still declare 2025.10.2 as the minimum supported HA for end users — unchanged.
• Supersedes the earlier revert + renovate-disable approach (history was force-pushed).
• HA is deliberately renovate-disabled in renovate.json, so this bump is manual — as expected.
• HA 2026.6.0+ pin aiodns==4.0.4 and could be a follow-up bump.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.