App 2.11.0, server 2.3.0: live data straight to ABRP; settings regrouped

ABRP keeps getting live data while the car server is down: with an ABRP
API key and user token set in the app (Live data tab, or abrp_api_key /
abrp_token in the config file), the car sends the newest sample to ABRP
itself at every upload. It tells the server the newest sample ABRP took
(abrpSentUtc), and the server forwards only newer ones, so ABRP gets
each sample once. Without credentials in the app the server forwards
everything, as before. The credentials sit in encrypted storage, go in
the request body, and neither they nor ABRP's answer are logged.

Settings are grouped by what they are for:
- Live data (was Upload): on/off, ABRP credentials, upload frequency.
- Settings (replaces the Wi-Fi tab): full screen and voice key,
  usable capacity and manual SoH (were on Consumption), charging price
  (was on Charging), Wi-Fi.
Charging and Live data get icons of their own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QLJfZQZeAKAwSqViTmLzki

server/README.md

@@ -40,7 +40,9 @@ with (403 otherwise); the shared token works for any.
   a plausible time (before 2001, or more than an hour ahead) is dropped whole. The rest is stored
   and the answer is `200 {stored, droppedCount, dropped}`, even when nothing was usable, since
   the car would only send it again. The newest sample is forwarded to ABRP if it is under
-  5 minutes old and not ahead of the server's clock.
+  5 minutes old and not ahead of the server's clock. A car that sends to ABRP itself adds
+  `abrpSentUtc`, the newest sample ABRP took from it; only samples newer than that are
+  forwarded, so ABRP gets each one once.
 - `PUT /v1/consumption/daily` — one delta chunk of a day's consumption.
 - `PUT /v1/charging-sessions/{sessionId}` — a finished DC session with its curve.
 - `GET /v1/consumption/history/{installationId}` — the car reads its own totals back.