Config UI: Vehicle data mismatch

[naltatis]

Main UI uses polled data based on the loadpoint's poll configuration and estimation to avoid API rate limits, while Config UI makes live updates and shows raw data (ignoring limits) to verify configuration is working correctly.

Data retrieved by opening the Config UI is not used in the charging control loop - this is by design due to historical architecture decisions. Changing this would require significant refactoring and is currently low priority for us since it does not impact daily charging behavior.

Workaround: Configure poll settings under loadpoints to update vehicle data more frequently if needed.

Related: #24776, #24354