SolaX: align entity names with the cloud app

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.

  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 1 / Charge End 1  -> Force Charge Start / Force Charge End
  Discharge Start 1 / End 1      -> Allowed Discharge Start / End

"Feedin Priority" becomes "Feed-In Priority" everywhere, including the
remote control power control options, since it is a mode name in the app.

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

Every entity name spelling the state of charge as "SOC" now uses "SoC",
matching the app and the entities already renamed above: 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 left alone, 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 at
0x6D/0x6E and Allowed Discharge Start/End 2 at 0x6F/0x70) now use
active_when so they only exist while that switch is on, the same way the
app hides the second period. The Gen2/Gen3 period 2 times keep their old
behaviour - those models have no such switch.

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; that switch moves
to the Configuration section. A heating level setting
exists only for dual-battery systems (0x20A/0x20B per the V1.02 doc,
already exposed as Gen5/Gen6 readbacks); a Gen4 rejects that whole
register block, verified live.

Author: Bl00d-B0b