feat: honest install badge — classify store resolvability before the click

Split each flow's missing capabilities into store-resolvable ones
(amber chip + Install link, which now installs only those) and a
quiet 'not in store' chip whose tooltip explains the three recovery
paths in place: local install via chain install --link, adding the
providing store, or configuring the MCP/n8n integration. The
analyzer's not-in-store message names the same three paths (EN+DE).
Previously the list's Install action covered every missing
capability and could end in the hub's 'no store entry' error.

Also replace a private-looking capability example name in a doc
comment and test with a neutral placeholder. (0.25.0)

Signed-off-by: flemming-it <sf@flemming.it>

test/flow_analyzer_test.dart

@@ -135,13 +135,20 @@ steps:
 name: x
 steps:
   - id: c
-    use: htw.private/secret@^0.1
+    use: acme.internal/secret@^0.1
 '''));
       expect(r.issues, hasLength(1));
       final fixes = a.fixesFor(r.issues.first);
       expect(fixes, hasLength(1));
       expect(fixes.first, isA<AddModuleSourceFix>());
-      expect(r.issues.first.message, contains('Not in the store'));
+      // The message must explain all three recovery paths in place:
+      // local install, adding a store, configuring an integration.
+      expect(
+        r.issues.first.message,
+        contains('No configured store can install it'),
+      );
+      expect(r.issues.first.message, contains('chain install --link'));
+      expect(r.issues.first.message, contains('integration'));
     });
 
     test('did-you-mean wins over install/add-source when a near miss exists',