fix: don't flag another app's earlier alarm in the self-check

The system reports only the earliest alarm clock of any app, so an older
alarm left in the stock clock showed up as a problem the offered fix
couldn't solve. Another app's alarm at or before Clockula's next fire is
now fine; a missing registration, or anything later than ours, still is
a problem.

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

@@ -371,7 +371,7 @@
     <string name="selfcheck_oem_warn">Some manufacturers aggressively close background apps — see how to keep Clockula exempt</string>
 
     <string name="selfcheck_next_alarm_title">Next alarm, as the system sees it</string>
-    <string name="selfcheck_next_alarm_ok">Matches what Clockula scheduled</string>
+    <string name="selfcheck_next_alarm_ok">Agrees with what Clockula scheduled</string>
     <string name="selfcheck_next_alarm_problem">Doesn\'t match what Clockula scheduled — open the app to re-check</string>
 
     <!-- M10: widgets -->