Test minimum and current Home Assistant runtimes in CI

[PrzemyslawKlys]

Summary

• add an explicit minimum lane on Python 3.12 and Home Assistant 2024.4.0
• add a current lane on the latest Python 3.14 patch and latest released Home Assistant
• keep the conservative Ruff syntax target unchanged

This is a stacked follow-up to #6987 and should be considered after its compatibility-floor correction. If the extra lane is not useful for this repository, feel free to close this PR.

Why

The minimum lane protects the compatibility declared in hacs.json. The current lane provides early warning for Home Assistant API, Python, and dependency changes before those combinations become the repository's minimum.

Using 3.14 rather than an exact patch lets actions/setup-python keep the lane on the newest available Python 3.14 patch automatically.

Validation

• Python 3.12.12 with Home Assistant 2024.4.0: integration config-flow import succeeded; 34 tests passed
• Python 3.14.2 with Home Assistant 2026.7.2: integration config-flow import succeeded; 34 tests passed
• dependency checks, workflow YAML formatting, actionlint, and applicable pre-commit hooks passed

Type of change

• New source
• Bug fix / source fix
• Documentation update
• Other: CI compatibility coverage

[markvp]

Thanks @PrzemyslawKlys. #6987 has merged, so master now carries the HA 2024.4 / Python 3.12 floor and this branch's validate.yaml conflicts with it. Could you merge master in and keep your matrix python_version (the min/current lanes supersede the single hardcoded 3.12 that landed via #6987)? hacs.json and requirements.txt already match master now, so only validate.yaml needs resolving.

One small thing on the matrix: the current lane pins Python 3.14 — is HA installing and running cleanly there, or should it track 3.13? No worries if CI is green on it.

Once it's conflict-free I'll get it merged. Thanks!