fix: add starterProjects to AI stacks for command palette visibility (#704)

Devfile commands are unavailable in the Che command palette when a
workspace has no starterProjects section (eclipse-che/che#23479).
Add each stack's upstream repo as a starter project.

Signed-off-by: Oleksii Kurinnyi <okurinny@redhat.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: akurinnoy

stacks/hermes/1.0.0/devfile.yaml

@@ -32,6 +32,12 @@ metadata:
 attributes:
   controller.devfile.io/storage-type: per-workspace
 
+starterProjects:
+  - name: hermes-agent
+    git:
+      remotes:
+        origin: https://github.com/che-incubator/hermes-placeholder.git
+
 components:
   - name: tools
     container:

stacks/openclaw/1.0.0/devfile.yaml

@@ -32,6 +32,12 @@ metadata:
 attributes:
   controller.devfile.io/storage-type: per-workspace
 
+starterProjects:
+  - name: openclaw
+    git:
+      remotes:
+        origin: https://github.com/che-incubator/openclaw-placeholder.git
+
 components:
   - name: tools
     container:

stacks/picoclaw/1.0.0/devfile.yaml

@@ -31,6 +31,12 @@ metadata:
 attributes:
   controller.devfile.io/storage-type: per-workspace
 
+starterProjects:
+  - name: picoclaw
+    git:
+      remotes:
+        origin: https://github.com/sipeed/picoclaw.git
+
 components:
   - name: tools
     container:

stacks/zeroclaw/1.0.0/devfile.yaml

@@ -30,6 +30,12 @@ metadata:
 attributes:
   controller.devfile.io/storage-type: per-workspace
 
+starterProjects:
+  - name: zeroclaw
+    git:
+      remotes:
+        origin: https://github.com/zeroclaw-labs/zeroclaw.git
+
 components:
   - name: tools
     container: