v0.10.0: ITD 511 official API adapter (events + advisories + cameras) (#85)

First official-state-DOT-API pattern landing. Two adapters in one PR:

- itd_511 (event-class): polls Events (60s) + Advisories (300s) from
  https://511.idaho.gov/api/v2/get/{event,alerts}. Decodes EncodedPolyline
  to LineString via the polyline lib (bookend LineString or Point fallback);
  ITD Severity string mapped None->1 / Minor->2 / Major->3 with
  IsFullClosure=true forcing 3 regardless; RecurrenceSchedules /
  Restrictions / DetourPolyline pass through unmodified. Advisories ship
  as structural pass-through under data.advisory since the upstream
  /alerts endpoint currently returns []; per-record try/except keeps a
  surprise shape from sinking the cycle when ITD posts its first one.

- itd_511_cameras (telemetry-class): polls Cameras (600s). One event per
  camera per UTC day; image URL passes straight through to <img src>.
  Region uniform US-ID with data.source_jurisdiction preserving the raw
  upstream Source field for the ~1.2% cross-DOT border-region mirrors
  (UDOT / ODOT / WYDOT / WSDOT / NDot / MTD / DriveBC / Lemhi County).

Subject convention (v0.9.20 forward): central.traffic.<event_type>.us.id
and central.traffic_cameras.us.id.<camera_id>. Castle Rock state_511_atis
keeps its bare-state subject; consumers stay on central.traffic.>
wildcards during the A/B comparison window.

Retry predicate tightened from the Castle Rock / TomTom precedent: 5xx +
connection / timeout retry; 4xx other than 429 skip-with-warn (don't
burn quota on permanent errors); 429 honors Retry-After once then
retries. API key (alias 'idaho_511') travels in the ?key= query string,
so every error log path runs through self._redact() to scrub the URL.

Both adapters ship disabled; operator enables via GUI after registering
the API key with 'python -m set_api_key idaho_511'. Reuses existing
CENTRAL_TRAFFIC and CENTRAL_TRAFFIC_CAMERAS streams -- no archive
restart needed.

Scope-cap exception: this PR is ~1.5k lines vs. the standard 500-line
cap, authorized as a one-time exception for the first
official-state-DOT-API pattern landing. Two adapters + their tests +
real-API fixtures naturally exceed the v0.9.x adapter-cap budget.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

tests/test_events_feed_frontend.py

@@ -1147,6 +1147,8 @@ _SAMPLE_INNER = {
     "tomtom_flow": {"road_category": "primary", "relative_speed": 0.11},
     "tomtom_incidents": {"description": "Roadworks", "from": "Early Road", "to": "Slade Road"},
     "state_511_atis_cameras": {"location_description": "I-84 Mountain Home", "camera_id": 42},
+    "itd_511": {"event_type_short": "work_zone", "roadway_name": "I-84"},
+    "itd_511_cameras": {"location": "I-84 Mountain Home", "camera_id": 42},
 }
 
 # Exact expected subjects for the deterministic adapters. swpc_alerts is omitted
@@ -1169,6 +1171,8 @@ _EXPECTED_SUBJECT = {
     "tomtom_flow": "Traffic flow (primary) — 11% of free-flow",
     "tomtom_incidents": "Roadworks on Early Road → Slade Road",
     "state_511_atis_cameras": "Camera: I-84 Mountain Home",
+    "itd_511": "Road work on I-84",
+    "itd_511_cameras": "Camera: I-84 Mountain Home",
 }