fix(auto): guard shipped resources, walk favourite groups when skipping

History review requested by the owner: when and why did the Android Auto
UI stop working.

ANSWER: 31 July, commit 2540556, "give the equalizer actions distinct,
state-aware icons".

  9eff760 (31-07)  androidIcon: 'drawable/ic_stat_pluriwave'  -> in the APK
  2540556 (31-07)  androidIcon: 'drawable/ic_auto_eq_on'      -> NEVER in it

That commit swapped a drawable that shipped for two that the stale CI
resource cache never included. From that moment getResourceId returned 0,
PlaybackStateCompat.CustomAction.Builder threw, and the throw aborted
AudioService.setState before the session was published -- so every Android
Auto symptom chased since is one line of that commit. The bitter part is
that 2540556 was itself a fix for a report about two identical icons.

Three changes.

1. CI guard. The build now unzips the release APK and fails if a drawable
resolved by NAME at runtime is missing. Resolution by name cannot fail at
compile time -- it fails in the car, silently, with id 0. This class of
bug shipped undetected for a week; it cannot ship again.

2. Skipping stations now walks the favourites GROUP first, as requested:
group -> all favourites -> my stations -> catalogue. Two deliberate
exclusions, both tested: `sinAsignarId` is the ABSENCE of a group, not a
group, so those walk all favourites; and a one-member group falls through
too, or both buttons would be dead ends. The group is read from the
FAVOURITE record, never from the playing station -- that one is rebuilt by
emisoraDesdeMediaItem, which carries no group id and would always report
"unfiled".

3. Diagnostics on the station skip. It was reported as doing nothing for
radio, and every early return in that method is silent: an empty list and
a single-entry list look identical from outside. The log now names which
one fired, so the next capture answers it instead of another hypothesis.

Tests: 1161 -> 1165.

.gitea/workflows/build.yml

@@ -134,6 +134,36 @@ jobs:
       - name: Build APK release
         run: flutter build apk --release
 
+      # Guardian de recursos: el APK debe contener los drawables que el codigo
+      # resuelve POR NOMBRE en runtime (getResources().getIdentifier).
+      #
+      # Un nombre que no resuelve devuelve id 0, y eso no falla la
+      # compilacion: falla en el coche. Concretamente
+      # PlaybackStateCompat.CustomAction.Builder lanza con icono 0, ese throw
+      # aborta AudioService.setState antes de activar la sesion de medios, y
+      # Android Auto se queda con la interfaz congelada. Paso exactamente eso
+      # entre el 31-07 (commit 2540556) y el 07-08 sin que nada lo detectara.
+      #
+      # Anadir un drawable nuevo referenciado por nombre => anadirlo aqui.
+      - name: Verificar recursos criticos en el APK
+        run: |
+          APK=build/app/outputs/flutter-apk/app-release.apk
+          FALTAN=0
+          for RECURSO in ic_auto_eq_on ic_auto_eq_off ic_stat_pluriwave; do
+            if unzip -l "$APK" | grep -q "res/drawable/$RECURSO.xml"; then
+              echo "OK      res/drawable/$RECURSO.xml"
+            else
+              echo "FALTA   res/drawable/$RECURSO.xml"
+              FALTAN=1
+            fi
+          done
+          if [ "$FALTAN" -ne 0 ]; then
+            echo ""
+            echo "Hay drawables resueltos por nombre que NO estan en el APK."
+            echo "En runtime resolveran a id 0 y tumbaran la sesion de medios."
+            exit 1
+          fi
+
       - name: Build AAB release
         run: flutter build appbundle --release