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

k8s/secrets/secrets.example.yaml

@@ -26,7 +26,8 @@ stringData:
   # Approves a car on your phone when it pairs by QR code (at least 12 characters). Leave it
   # empty to switch pairing off; then only the INGEST_TOKEN above works.
   APPROVAL_PASSWORD: CHANGE-ME-at-least-12-characters
-  # Your ABRP credentials. Leave either empty to switch forwarding off.
+  # Your ABRP credentials. Leave either empty to switch forwarding off. Keep them set even
+  # when the app sends to ABRP itself: the server then forwards only what the car could not.
   ABRP_API_KEY: CHANGE-ME
   ABRP_USER_TOKEN: CHANGE-ME
   ABRP_MIN_INTERVAL_SECONDS: "5"