fix(release): ship the corrected HA floor in a tag, not just on main

5.2.0 declared "homeassistant": "2023.1.0" in hacs.json, which is the key HACS
gates installation on: a user on 2023.1-2024.3 was allowed to install the
integration and only then hit an ImportError, because config_flow.py imports
ConfigFlowResult and HA added that symbol in 2024.4.

The previous commit corrected hacs.json on main, which does not reach anyone.
HACS reads hacs.json at the version it is considering, not from the default
branch -- version_to_download() resolves to the latest release tag and
async_get_hacs_json() fetches the file at that ref -- so the value that
actually gates an install is the one inside the tag. Confirmed against the
published files: main/hacs.json says 2024.4.0 while v5.2.0/hacs.json still
said 2023.1.0.

This patch release carries the correction inside the tag. Bumping
manifest.json to 5.2.1 in the same release is not decoration: HACS compares the
installed manifest version against the tag, so without the bump an existing
5.2.0 install would have no reason to re-fetch and would keep the bad gate.

Author: ngoviet

docs/DEVELOPMENT_NOTES.md

@@ -135,6 +135,15 @@ at setup — an install error rather than a "needs a newer HA" message.
 A version floor written down twice drifts the same way the version number did.
 If you change one, change `hacs.json` and the README together.
 
+**A metadata fix on `main` does not reach HACS users until it is in a tag.**
+HACS reads `hacs.json` *at the version it is considering*, not from the default
+branch: `version_to_download()` resolves to the latest release tag and
+`async_get_hacs_json()` fetches the file at that ref. Correcting `main` alone
+changes nothing for anyone — `raw.githubusercontent.com/.../main/hacs.json` and
+`.../v5.2.0/hacs.json` can disagree, and HACS only ever reads the second. Ship a
+patch release with the corrected metadata; raising `manifest.json` in the same
+release is what makes the existing install look stale enough to update.
+
 ## A non-finite vendor number is not a reading
 
 `json.loads` accepts the bare `NaN` / `Infinity` / `-Infinity` literals, so a

manifest.json

@@ -18,5 +18,5 @@
         "paho-mqtt>=1.6.0",
         "crcmod>=1.7"
     ],
-    "version": "5.2.0"
+    "version": "5.2.1"
 }