fix: show resolved hash for branch inputs in SUSFS Configuration summary

Distinguishes three input cases in the Build plan summary SUSFS
Configuration loop using regex on the raw input value.

Changes in build-kernel-release.yml:
- Build plan summary: SUSFS Configuration loop now uses three distinct
  display formats based on input type:
  auto (empty input)     → 🔄 auto (`<hash>`)
  hash (40-char hex)     → 📌 `<hash>`
  branch (any other)     → 🔀 `<branch>` (`<resolved hash>`)

Author: luigimak

.github/workflows/build-kernel-release.yml

@@ -353,11 +353,16 @@ jobs:
           for key in "${active_keys_display[@]}"; do
             value="${susfs_inputs[$key]:-}"
             fetched_hash="${step_hashes[$key]:-unknown}"
-            
-            if [ -n "$value" ]; then
+
+            if [ -z "$value" ]; then
+              # Auto: no input > hash resolved by ls-remote
+              echo "- $key: 🔄 auto (\`$fetched_hash\`)" >> $GITHUB_STEP_SUMMARY
+            elif [[ "$value" =~ ^[0-9a-f]{40}$ ]]; then
+              # Manual 40-char hash > direct passthrough
               echo "- $key: 📌 \`$value\`" >> $GITHUB_STEP_SUMMARY
             else
-              echo "- $key: 🔄 auto → \`$fetched_hash\`" >> $GITHUB_STEP_SUMMARY
+              # Branch name > show branch + resolved hash
+              echo "- $key: 🔀 \`$value\` (\`$fetched_hash\`)" >> $GITHUB_STEP_SUMMARY
             fi
           done