extract the map workspace's domain layer out of the component

MapWorkspace.tsx opened with ~590 lines of theme catalogue, dataset matching
and label formatting above a 3.200-line component. None of it is React, all of
it is independently testable, and both render paths read from it, so it belongs
beside the pure helpers that already live in mapWorkspaceUtils.

The contract tests that read MapWorkspace.tsx would have gone red for a move
that changes no behaviour at all — 24 of them. That is the brittleness the
frontend_contract helper exists to remove, so it gains read_map_workspace():
the workspace is one feature spread over several modules, and a contract
belongs to the feature rather than to whichever file currently holds it.

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

backend/tests/test_sprint236_bathymetry_expansion.py

@@ -31,6 +31,7 @@ if str(SCRIPTS) not in sys.path:
     sys.path.insert(0, str(SCRIPTS))
 
 import provision_flanders_geographic_scope as flanders_scope  # noqa: E402
+from tests.frontend_contract import read_map_workspace
 
 
 class BinaryResponse:
@@ -463,9 +464,7 @@ def test_frontend_uses_partitioned_bathymetry_selection_for_regional_scope() ->
     focus = (
         ROOT / "frontend" / "src" / "config" / "primaryFocus.ts"
     ).read_text(encoding="utf-8")
-    map_workspace = (
-        ROOT / "frontend" / "src" / "components" / "map" / "MapWorkspace.tsx"
-    ).read_text(encoding="utf-8")
+    map_workspace = read_map_workspace()
     theme_hook = (
         ROOT / "frontend" / "src" / "hooks" / "useMapThemeSelectionInsights.ts"
     ).read_text(encoding="utf-8")