record-tester: Use different dedup key when lopri

Otherwise it could get confusing that the incident with
the [LOPRI] prefix sends a high urgency alert.

internal/app/recordtester/continuous_record_tester.go

@@ -126,10 +126,15 @@ func (crt *continuousRecordTester) sendPagerdutyEvent(rt IRecordTester, err erro
 	if crt.pagerDutyIntegrationKey == "" {
 		return
 	}
+	severity, lopriPrefix, dedupKey := "error", "", fmt.Sprintf("cont-record-tester:%s", crt.host)
+	if crt.pagerDutyLowUrgency {
+		severity, lopriPrefix = "warning", "[LOPRI] "
+		dedupKey = "lopri-" + dedupKey
+	}
 	event := pagerduty.V2Event{
 		RoutingKey: crt.pagerDutyIntegrationKey,
 		Action:     "trigger",
-		DedupKey:   fmt.Sprintf("cont-record-tester:%s", crt.host),
+		DedupKey:   dedupKey,
 	}
 	if err == nil {
 		event.Action = "resolve"
@@ -139,10 +144,6 @@ func (crt *continuousRecordTester) sendPagerdutyEvent(rt IRecordTester, err erro
 		}
 		return
 	}
-	severity, lopriPrefix := "error", ""
-	if crt.pagerDutyLowUrgency {
-		severity, lopriPrefix = "warning", "[LOPRI] "
-	}
 	event.Payload = &pagerduty.V2Payload{
 		Source:    crt.host,
 		Component: crt.pagerDutyComponent,