Fix wheel/panel layering, add bottom-bar background, and full-screen charts

- Wheels/readouts now add max(MediaQuery.padding.left/right) on both sides
  symmetrically (HTML prototype: max(env(safe-area-inset-left),
  env(safe-area-inset-right))), so a front-camera cutout in landscape
  doesn't sit behind the altitude wheel, and both sides stay in sync.
- WaypointListPanel is now pushed via Navigator (PageRouteBuilder + fade)
  instead of being an internal Stack overlay in PlanScreen. It was
  rendering *under* AppShell's TopModeBar before, since TopModeBar is
  always the last (topmost) child of AppShell's own Stack regardless of
  what PlanScreen draws internally - a plain bool flag inside PlanScreen
  had no way to paint above a sibling higher up the tree. A pushed route
  paints above the entire invoking route's content by construction, so
  this was the actual fix rather than reshuffling Z-order inside PlanScreen.
- Extracted DefaultDroneProfile (T1 Ranger constants) out of PlanScreen's
  private statics into lib/domain/mission/, since WaypointListPanel now
  needs the same values to compute its own route geometry reactively
  (previously passed down as a vertexBad/altMin/altMax/... snapshot, which
  would have gone stale while the panel was open across a route boundary).
- Bottom bar now has the prototype's rgba(15,15,15,0.72) background
  (previously fully transparent outside the stats pill), and gained
  MiniAltitudeProfile - the non-interactive height-profile sparkline
  that sits above the stats row.
- Added the Altitude/Speed full-screen chart tabs (FullValueChart):
  drag any waypoint's point to adjust its altitude/speed, X position
  proportional to cumulative route distance, matching the prototype's
  buildFullChart()/attachChartDrag(). Terrain overlay and wind diamonds
  from the prototype aren't ported - terrain (doc 3.9) and wind (doc 3.8)
  systems don't exist yet in the Flutter app.
- RouteGeometry now also exposes legClimbBad (was computed internally but
  not surfaced), needed by both the mini profile and the chart tabs.

Discovered while updating the widget tests: a single tester.pump() after
tapping something that triggers Navigator.push/pop isn't enough - the
push/pop itself needs a frame to register before a duration-based pump
can animate it, so both are needed in sequence. Added 2 new tests for the
chart tabs; all 17 tests and flutter analyze pass. Verified all four
changes on the Pixel_10a emulator: wheels, opaque bottom bar with the
mini profile, the list panel now fully covering the top bar (confirmed by
its complete absence while the panel is open), and dragging points on
both chart tabs.

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

app/lib/domain/mission/route_geometry.dart

@@ -15,7 +15,11 @@ class RouteSegment {
 }
 
 class RouteGeometry {
-  const RouteGeometry({required this.segments, required this.vertexBad});
+  const RouteGeometry({
+    required this.segments,
+    required this.vertexBad,
+    required this.legClimbBad,
+  });
 
   final List<RouteSegment> segments;
 
@@ -25,7 +29,12 @@ class RouteGeometry {
   /// Kurswinkel ist zu scharf).
   final List<bool> vertexBad;
 
-  static const empty = RouteGeometry(segments: [], vertexBad: []);
+  /// Pro Streckenabschnitt (Index i verbindet Wegpunkt i und i+1): true,
+  /// wenn die noetige Steig-/Sinkrate das Limit der Drohne ueberschreitet.
+  final List<bool> legClimbBad;
+
+  static const empty =
+      RouteGeometry(segments: [], vertexBad: [], legClimbBad: []);
 }
 
 class _V {
@@ -183,7 +192,11 @@ RouteGeometry buildRouteGeometry(
     }
   }
 
-  return RouteGeometry(segments: segments, vertexBad: vertexBad);
+  return RouteGeometry(
+    segments: segments,
+    vertexBad: vertexBad,
+    legClimbBad: legClimbBad,
+  );
 }
 
 _V _pointOnCircle(_V center, double radius, double angle) =>