v1.15.4: restore BLOKYSPOTREBY-OK naming

Bugfix: restore v1.15.1 naming for BLOKYSPOTREBY-OK (heating-circuit status)

v1.15.2 forced BLOKYSPOTREBY-OK (the heating-circuit "is HP serving this circuit?" status flag from okruh.xml) into a binary sensor with the custom name "TČ topí okruh" / "HP heating circuit". This broke existing automations and dashboards that referenced the v1.15.1 entity_id (e.g. sensor.heating_circuit_switch).

In v1.15.4 the override for this single field is dropped. The descriptor in okruh.xml already provides:

<row prop="BLOKYSPOTREBY-OK" text="Vypínač okruhu" text_en="Heating circuit switch">

…which the descriptor parser turns into a read-only sensor with that name — the same behavior as v1.15.1. Home Assistant will re-register it under the original sensor.*_heating_circuit_switch entity_id.

Scope

• Only BLOKYSPOTREBY-OK (heating circuit, from okruh.xml) is affected.
• BLOKYSPOTREBY1-OK, BLOKYSPOTREBY2-OK, BLOKYSPOTREBY3-OK, BLOKYSPOTREBY6-OK, BLOKYSPOTREBY7-OK stay as binary sensors with the descriptive names added in v1.15.2. Their descriptors only declare the prop at the block level and provide no row-level text attributes, so without the override they would fall back to _BOOL_i-suffix parsing as writable switches.
• All BLOKYSPOTREBY*-UTLUM attenuation entries are unchanged.

Upgrade notes

If you had added a manual entity_id override in Home Assistant's entity registry for the v1.15.3 binary_sensor.<device>_tc_topi_okruh, you may want to clear it so HA picks up the restored sensor.*_heating_circuit_switch entity_id.