fix(audio): make the audio diagnostics visible in release builds

Every diagnostic line in the audio path used `dart:developer`'s `log()`.
That function writes to the VM service, which a RELEASE build does not
have — so in the only build that ever runs in a car, all eleven of them
went nowhere. `debugPrint`/`print` do reach logcat in release; `log()`
does not.

That includes the two channels built specifically to end the guessing:
- `registrarErrorAudioService`, which subscribes to
  `AudioService.asyncError` so the plugin's swallowed platform exceptions
  stop vanishing (b0271fa). It moved them from a dropped PublishSubject
  to a dropped log call.
- `_trazarEstadoPublicado`, the published-state trace added in 7054a4c to
  settle why the car's play button never becomes pause.

So "no evidence" was never a quiet app. It was an app writing its
evidence somewhere release builds discard. Several rounds of hypotheses
were argued without data that the app was already producing.

All eleven now use `debugPrint` with a `[PluriWave][Tag]` prefix, so one
filter catches the audio path and the existing alarm lines together:

  adb logcat | grep PluriWave

No behaviour changes. Tests: 1158, unchanged.

lib/servicios/arranque_audio.dart

@@ -1,5 +1,4 @@
 import 'dart:async';
-import 'dart:developer' as developer;
 
 import 'package:flutter/material.dart';
 
@@ -94,16 +93,18 @@ StreamSubscription<Object> observarErroresAudio(
   );
 }
 
-/// Default [observarErroresAudio] logger: one `[PluriWave]`-prefixed
-/// `developer.log` line per swallowed plugin exception, at the same
-/// `level: 900` (SEVERE) that `servicio_audio.dart`'s existing error lines
-/// use, so a single logcat/DevTools filter catches both.
+/// Default [observarErroresAudio] logger: one line per swallowed plugin
+/// exception.
+///
+/// Uses [debugPrint], NOT `dart:developer`'s `log`. That distinction is the
+/// whole reason this channel existed for weeks without ever producing a
+/// single line of evidence: `log()` writes to the VM service, which a
+/// RELEASE build does not have, so every exception this was built to catch
+/// was still being thrown away — just one layer further down than before.
+/// `debugPrint` reaches logcat in release, which is the only build that ever
+/// runs in the car.
 void registrarErrorAudioService(Object error) {
-  developer.log(
-    '[PluriWave] AudioService.asyncError: $error',
-    name: 'ArranqueAudio',
-    level: 900,
-  );
+  debugPrint('[PluriWave][ArranqueAudio] AudioService.asyncError: $error');
 }
 
 /// Minimal branded bootstrap widget for the degraded path (Design "still