fix(alarms): keep a skip on the next ring after any edit, and say when a pause ends

Moving the time or changing the days left a pending skip pointing at the
old sequence, so the skipped day could ring at its new time. Every editor
change that can move a fire time now re-arms the skip.

A pause under way now reads "Paused, back on Thu, Oct 29" instead of
naming its last day, which read as the day it ends before. Reopening a
begun pause keeps its start, the date pickers take their bounds from the
clock when they open, and the dismiss chooser shows the scheduled date and
pause like the list does.

app/src/main/res/values/strings.xml

@@ -122,8 +122,8 @@
     <string name="alarm_scheduled_for">Scheduled for %1$s</string>
     <!-- %1$s is a date range such as "Oct 26 – 28" -->
     <string name="alarm_paused_dates">Paused %1$s</string>
-    <!-- %1$s is a date such as "Oct 28": the pause has already begun -->
-    <string name="alarm_paused_until">Paused until %1$s</string>
+    <!-- %1$s is the first date the alarm rings again, such as "Thu, Oct 29": the pause has already begun -->
+    <string name="alarm_paused_back_on">Paused, back on %1$s</string>
     <string name="alarm_summary_separator" translatable="false">" \u00b7 "</string>
 
     <!-- M5: the alarm editor -->