feat(workspace): sealed-area names are confidential by default

The switcher listed sealed areas by name ('lbs', 'stromnetz') on
any glance or screenshot — but the names themselves often carry
client/mandate identity (usertest security finding). The sealed
section now renders one aggregated row ('2 sealed areas') with a
deliberate 'Show names' reveal per menu opening; selection still
pops the regular s:<slug> value. Settings -> Security gains 'list
sealed areas with their names right away' (WorkspacePrefs,
SidebarPrefs pattern, default off).

The aggregate row wraps to two lines — popup menus cap their
width and action texts must never be truncated (the first cut
showed '1 abgeschotte…' in the proof shot). Guard: switcher tests
cover aggregated-until-reveal and the Settings toggle; the old
direct-listing test now asserts the reveal contract. DE+EN.

Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com>

lib/l10n/app_en.arb

@@ -1838,6 +1838,11 @@
   "runsPhaseUnknown": "Unknown",
   "navRuns": "Runs",
   "workspaceSealedHeader": "SEALED AREAS",
+  "workspaceSealedAggregate": "{n, plural, =1{1 sealed area} other{{n} sealed areas}}",
+  "@workspaceSealedAggregate": {"placeholders": {"n": {"type": "int"}}},
+  "workspaceSealedRevealAction": "Show names",
+  "settingsSealedNamesTitle": "List sealed areas with their names right away",
+  "settingsSealedNamesBody": "Area names can be sensitive (client/mandate identity). By default the workspace switcher shows them aggregated; the names appear only after a click.",
   "workspaceSealedRunning": "running",
   "workspaceSealedStopped": "stopped",
   "workspaceSealedRunningHint": "The sealed area runs as its own hub process. Selecting it switches in.",