Fix broken map rendering, split GPS cleanup, receipt parser and design backlog

Leaflet's stylesheet was appended to document.head, so it never reached the
panel's shadow root: .leaflet-tile{position:absolute} never applied, tiles laid
out as in-flow images (~1040px inside a 190px box) and the marker pane ended up
far below the visible area. That is the real cause of the long-standing
"fragmented Leaflet rendering" finding and of the invisible vehicle pin - every
tile request had actually succeeded. The stylesheet now goes into the shadow
root and is awaited before the map is built.

Also in this round:
- Map tiles are always light (Google-Maps-style), no dark variant at night.
- Vehicle marker uses the real CI poi-car icons (poi-car-l >=34px, poi-car-s
  below), with a white halo so the outline stays readable on tiles.
- Removed the obsolete combined STANDORT_TRACKER field; only the split
  lat/lon sensors remain.
- Receipt upload: widened the try block so base64/save failures surface, and
  the frontend call site now reports a rejected service call.
- Generic receipt parser: total detection is line-based (letter-spaced
  headings, no more matching the SUMME-EUR column header, tax lines excluded),
  address heuristic handles 4-digit postcodes and single-line address blocks,
  and "Preis/L" matches without a spelled-out "Liter".
- Design backlog: red hairline frame on list rows (delete button bled through
  at fractional row heights) and select fields now use the grey background box.

Shell 10-receipt regression suite still passes; all changes verified live in
the audi_ha_test container.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

homeassistant/pyscript/modules/entitaeten.py

@@ -109,18 +109,14 @@ FELDER = [
      "hinweis": "Meldet die Integration oft als negativen Countdown - die App zeigt nur den Betrag.",
      "domains": ["sensor"], "device_classes": ["distance"], "units": ["km", "mi"], "liste": False, "pflicht": False,
      "stichworte": ["inspektion", "inspection", "distance", "strecke"]},
-    {"key": "STANDORT_TRACKER", "label": "GPS-Standort", "gruppe": "standort",
-     "hinweis": "Braucht latitude/longitude-Attribute (HA-Konvention für device_tracker).",
-     "domains": ["device_tracker"], "device_classes": [], "units": [], "liste": False, "pflicht": False,
-     "stichworte": ["standort", "gps", "tracker", "position", "ortung"]},
     {"key": "STANDORT_LAT_SENSOR", "label": "GPS-Standort: Breitengrad", "gruppe": "standort",
-     "hinweis": "Nur nötig, falls die Integration Breiten-/Längengrad als zwei eigene Sensoren statt als Attribute einer GPS-Standort-Entity liefert (z. B. flespi).",
+     "hinweis": "Breitengrad als eigener Sensor (z. B. flespi).",
      "domains": ["sensor"], "device_classes": [], "units": [], "liste": False, "pflicht": False,
-     "stichworte": ["breitengrad", "latitude", "lat"]},
+     "stichworte": ["breitengrad", "latitude", "lat", "standort", "gps", "position", "ortung"]},
     {"key": "STANDORT_LON_SENSOR", "label": "GPS-Standort: Längengrad", "gruppe": "standort",
-     "hinweis": "Nur nötig, falls die Integration Breiten-/Längengrad als zwei eigene Sensoren statt als Attribute einer GPS-Standort-Entity liefert (z. B. flespi).",
+     "hinweis": "Längengrad als eigener Sensor (z. B. flespi).",
      "domains": ["sensor"], "device_classes": [], "units": [], "liste": False, "pflicht": False,
-     "stichworte": ["längengrad", "longitude", "lon", "lng"]},
+     "stichworte": ["längengrad", "longitude", "lon", "lng", "standort", "gps", "position", "ortung"]},
 ]
 
 # Mehrere @state_trigger(f"...")-Dekoratoren (fahrterkennung.py,