fix(vacaciones): edit and delete vacation ranges

Vacaciones ranges could be created but never edited or removed --
EstadoAlarmas already had crearRangoVacaciones/eliminarRangoVacaciones
with no UI affordance reaching them, and no update path at all.

Add EstadoAlarmas.editarRangoVacaciones and wire tap-to-edit /
swipe-to-delete (with confirmation) onto every range card, mirroring
the alarm list's own Dismissible + confirm-dialog pattern exactly. This
covers the active-range hero too: a freshly created range is active
immediately and only ever renders there, never in the
scheduled/past lists, so it needed the same affordances or a user's
very first range could never be fixed.

lib/estado/estado_alarmas.dart

@@ -354,6 +354,19 @@ class EstadoAlarmas extends ChangeNotifier {
     await guardarVacaciones(nuevos);
   }
 
+  /// Issue 1 (feedback-pruebas): replaces the range with the same [id] in
+  /// place -- the counterpart `crearRangoVacaciones`/`eliminarRangoVacaciones`
+  /// were missing before this fix, leaving no way to fix a mistake in an
+  /// already-saved range (including the currently ACTIVE one, since a
+  /// freshly created range starts active immediately).
+  Future<void> editarRangoVacaciones(RangoVacaciones rango) async {
+    final nuevos = [
+      for (final actual in _vacaciones)
+        if (actual.id == rango.id) rango else actual,
+    ];
+    await guardarVacaciones(nuevos);
+  }
+
   // ── Vacation queries (design ADR-6, WU9) ──────────────────────────────
   // Four PURE queries: none writes, none reschedules, none touches the
   // native bridge. Read-only over `_alarmas`/`_vacaciones`. Every method