fix(alarm): handle snooze reschedule failures instead of silently dropping them

posponerAlarma() and posponerProximaDesdePreaviso() called the native
scheduler with no error handling, unlike guardarAlarma(). When the
native call failed (e.g. revoked exact-alarm permission), the
exception escaped before notifyListeners() ran, leaving the alarm
list stuck on stale data with no real alarm scheduled and no snooze
countdown notification.

Both methods now mirror guardarAlarma()'s pattern: permission
pre-check, try/catch into _error, and an unconditional
notifyListeners() so the UI always reflects the outcome. Failures
surface via SnackBar in the ringing screen and in app.dart's
postpone-next handler.

test/helpers/fakes_alarmas.dart

@@ -17,6 +17,11 @@ class FakePuertoAlarmasAndroid implements PuertoAlarmasAndroid {
   bool ignoraOptimizacionBateria = true;
   int solicitudesExencionBateria = 0;
 
+  /// Test-only failure switch (Design D7): when true, [programar] throws
+  /// instead of scheduling, enabling failure-path coverage that the fake
+  /// could not otherwise produce.
+  bool fallaProgramar = false;
+
   /// Simulates a native -> Flutter `alarmFired` MethodChannel event.
   void emitirEvento(EventoAlarmaAndroid evento) => _eventos.add(evento);
 
@@ -28,6 +33,9 @@ class FakePuertoAlarmasAndroid implements PuertoAlarmasAndroid {
 
   @override
   Future<void> programar(AlarmaMusical alarma) async {
+    if (fallaProgramar) {
+      throw StateError('fake programar failure');
+    }
     programadas.add(alarma);
   }