BUGFIX: Mark the rule's restoration process as completed always

In #13980 I introduced a change to reduce the number of queries executed when we restore alert statuses.

With this, the querying semantics changed as we now need to go through all series before we enter the alert restoration loop and I missed the fact that exiting early when there are no rules to restore would lead to an incomplete restoration.

An alert being restored is used as a proxy for "we're now ready to write `ALERTS/ALERTS_FOR_SERIES` metrics" so as a result we weren't writing the series if we didn't restore anything the first time around.

Signed-off-by: gotjosh <josue.abreu@gmail.com>

rules/group.go

@@ -672,6 +672,7 @@ func (g *Group) RestoreForState(ts time.Time) {
 				"stage", "Select",
 				"err", err,
 			)
+			alertRule.SetRestored(true)
 			continue
 		}
 
@@ -684,6 +685,7 @@ func (g *Group) RestoreForState(ts time.Time) {
 		// No results for this alert rule.
 		if len(seriesByLabels) == 0 {
 			level.Debug(g.logger).Log("msg", "Failed to find a series to restore the 'for' state", labels.AlertName, alertRule.Name())
+			alertRule.SetRestored(true)
 			continue
 		}
 

rules/manager_test.go

@@ -482,6 +482,9 @@ func TestForStateRestore(t *testing.T) {
 				return labels.Compare(got[i].Labels, got[j].Labels) < 0
 			})
 
+			// In all cases, we expect the restoration process to have completed.
+			require.Truef(t, newRule.Restored(), "expected the rule restoration proccess to have completed")
+
 			// Checking if we have restored it correctly.
 			switch {
 			case tt.noRestore: