fix(alarms): open the ring screen when the editor's Delete is refused

Deleting a ringing alarm from the editor is refused, and a refused tap did nothing visible. It now opens the ring screen, the same way out the list's card offers.

docs/ARCHITECTURE.md

@@ -1725,7 +1725,7 @@ challenge. The engine re-checks under its lock (`delete(id, unlessRinging = true
 so a swipe released just as the alarm fires, before the list has caught up,
 deletes nothing and the card slides back. The editor's Delete passes the same
 flag: with its confirmation gone, one tap there would otherwise do what the
-swipe is kept from doing, so a ringing alarm is dealt with on its ring screen. Each is followed by a snackbar on the list ("07:00 alarm deleted",
+swipe is kept from doing, so a refused tap opens the ring screen instead, where the alarm is dealt with. Each is followed by a snackbar on the list ("07:00 alarm deleted",
 **Undo**), as in Google Clock. v1 asked before instead, on the argument that a
 mistaken delete is found at 07:00 rather than now. But a dialog catches no more
 than the snackbar does: both only catch the slip noticed in the moment, and a