Fix E2E select locator, remove maxspeed mode (data unavailable)

E2E fixes:
- Color mode select locator uses option[value='highway'] filter
  instead of fragile page.locator("select").last()

Removed maxspeed color mode:
- BRouter does not expose maxspeed in WayTags output despite the tag
  existing in its lookup table. The dummyUsage profile trick only
  affects cost calculation, not tiledesc output.
- Can revisit if BRouter adds maxspeed to WayTags in a future version
  or if we fork/patch the BRouter profiles more deeply.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

apps/planner/app/components/PlannerMap.tsx

@@ -376,7 +376,6 @@ export function PlannerMap({ yjs, onRouteRequest, highlightPosition, highlighted
   const [segmentBoundaries, setSegmentBoundaries] = useState<number[]>([]);
   const [surfaces, setSurfaces] = useState<string[]>([]);
   const [highways, setHighways] = useState<string[]>([]);
-  const [maxspeeds, setMaxspeeds] = useState<string[]>([]);
   const [colorMode, setColorMode] = useState<ColorMode>("plain");
   const [noGoDrawing, setNoGoDrawing] = useState(false);
   const toggleNoGoDraw = useCallback(() => setNoGoDrawing((v) => !v), []);
@@ -451,13 +450,6 @@ export function PlannerMap({ yjs, onRouteRequest, highlightPosition, highlighted
         setHighways([]);
       }
 
-      const maxspeedsJson = yjs.routeData.get("maxspeeds") as string | undefined;
-      if (maxspeedsJson) {
-        try { setMaxspeeds(JSON.parse(maxspeedsJson)); } catch { setMaxspeeds([]); }
-      } else {
-        setMaxspeeds([]);
-      }
-
       if (modeVal) setColorMode(modeVal);
     };
 
@@ -739,7 +731,6 @@ export function PlannerMap({ yjs, onRouteRequest, highlightPosition, highlighted
             colorMode={colorMode}
             surfaces={surfaces}
             highways={highways}
-            maxspeeds={maxspeeds}
           />
           <RouteInteraction
             coordinates={routeCoordinates}