SolaX: align entity names with the cloud app

[Bl00d-B0b]

Stacked on the sub-device series (#2279 → #2283 → #2284 → #2285 → #2286). Review the last commit only — the diff includes the parents until they merge.

Display names of the hybrid battery-mode settings now match what the SolaX cloud app shows, so a setting is called the same thing in both places. Keys and entity ids are unchanged.

Before	After
Selfuse Night Charge	Self Use Charge from Grid
Selfuse Discharge Min SOC	Self Use Min SoC
Selfuse Nightcharge Upper SOC	Self Use Charge Battery to
Feedin Discharge Min SOC	Feed-In Priority Min SoC
Feedin Nightcharge Upper SOC	Feed-In Priority Charge Battery to
Backup Discharge Min SOC	Backup Min SoC
Backup Nightcharge Upper SOC	Backup Charge Battery to
Charge Start/End 1 and 2	Force Charge P1/P2 Start/End
Discharge Start/End 1 and 2	Allowed Discharge P1/P2 Start/End

Select option values are deliberately untouched — Feedin Priority, Enabled Feedin Priority and the SOC-mode options keep their exact strings, since automations select options and match states by string. This PR changes nothing an automation can reference: entity ids, keys and option values are all unchanged; only display names move.

Self Use Charge Battery to only applies while Self Use night charge is enabled, so it uses active_when (from #2279) to follow that switch.

Every remaining entity name that spelled the state of charge as SOC now uses SoC — Min SoC, Restart SoC, Selfuse Backup SoC, Switch On SoC, Battery Charge Upper SoC, PeakShaving Max/Reserved SoC, Min Esc SoC, the Dual Battery Charge Upper SoC readbacks and the Remotecontrol Target/Minimum SoC numbers. Select option values such as Reference SOC are deliberately untouched, since automations match those by string.

Charge and Discharge Period2 becomes Charge/Discharge Period 2, and the four Gen4/Gen5/Gen6 times it controls — Force Charge Start/End 2 (0x6D/0x6E) and Allowed Discharge Start/End 2 (0x6F/0x70) — now use active_when so they only exist while that switch is on, matching how the app hides the second period. Gen2/Gen3 keep their old behaviour; those models have no such switch.

The period number sits before Start/End (P1/P2) so each period's pair sorts together in alphabetical entity lists, instead of all Ends grouping before all Starts.

The four Battery Heating times (0xD0–0xD3 → 0xA4–0xA7) become Battery Heating P1/P2 Start/End, matching the period scheme above, and only exist while the Battery Heating switch (0xCF → 0xA3) is on. A heating level (Low/Medium/High) setting exists only for dual-battery systems (0x20A/0x20B per the V1.02 protocol document, already exposed as Gen5/Gen6 readback sensors); a Gen4 rejects that whole register block, verified live.

[TCWORLD]

Automations that select that option by string need updating.

Please don't break everyone's automatons for something that is purely stylistic...

[Bl00d-B0b]

Fair point — agreed and fixed. The select option values (Feedin Priority, Enabled Feedin Priority) are back to their original strings, so nothing that automations reference changes: entity ids, keys and option values are all untouched by this PR. What remains is purely display names (friendly names shown in the UI), which HA doesn't use for automation matching. The description's breaking-change note is removed accordingly.