feat(sidebar): surface partial status for multi-container stacks (#1426)

Bulk stack-status aggregation collapsed a stack to "running" as soon as any
container was up, so a multi-container stack with crashed containers showed a
green UP pill and the degradation was invisible from the sidebar.

Add a crash-aware "partial" state: a stack is partial when at least one
container is running and at least one has genuinely failed (exited with a
non-zero code, dead, or crash-looping). Cleanly finished one-shot containers
(exit 0) and clean restart-policy cycling do not count, so an app with a
completed init job stays UP. The exit code is read from the container Status
string, so no extra inspect calls are needed.

Render partial as an amber PT pill with a hover tooltip showing the
running/total count, fold it into the Down filter (needs-attention), and treat
it as running for context-menu lifecycle actions so operators keep
stop/restart/update. The dashboard stack-health table, cross-node search rows,
and the command palette all pick up the new state through the shared status
surfaces.

frontend/src/components/EditorLayout/hooks/useStackActions.ts

@@ -261,7 +261,10 @@ export function useStackActions(options: UseStackActionsOptions) {
     editorState.envContent !== editorState.originalEnvContent;
 
   const getStackMenuVisibility = (file: string) => {
-    const status = stackListState.stackStatuses[file];
+    // A partial stack has running containers, so it shows the running-stack
+    // lifecycle actions (stop/restart/update) rather than deploy.
+    const raw = stackListState.stackStatuses[file];
+    const status = raw === 'partial' ? 'running' : raw;
     return {
       showDeploy: status !== 'running',
       showStop: status === 'running',