ci(folio): say what the android gate found, not why

The gate proves only that AddTransactionScreen is absent from the trace.
Claiming the run never got past login was an inference it cannot make: the
run that produced it had logged in and was stuck on the new account screen.
Name the routes the trace does record instead.

.github/scripts/folio-run.sh

@@ -192,7 +192,12 @@ if [ "$platform" = "android" ]; then
     *) echo "folio/android: the harness failed with exit $code" >&2; exit "$code" ;;
   esac
   if ! grep -q '"AddTransactionScreen"' "$trace"; then
-    echo "folio/android: the run never reached AddTransactionScreen, so it never got past login" >&2
+    # Where it stopped is a much longer question than this gate answers, so
+    # name the routes the trace holds and leave the diagnosis to the reader.
+    reached=$(grep -oE '"[A-Za-z0-9]+Screen"' "$trace" | tr -d '"' |
+      awk '!seen[$0]++' | paste -sd, -) || reached=""
+    echo "folio/android: the run never reached AddTransactionScreen over $steps steps" >&2
+    echo "folio/android: routes the trace does record: ${reached:-none}" >&2
     exit 1
   fi
   echo "folio/android: healthy run over $steps steps, reached the transaction screen"