fix filtering of provisionalScoreComplete logic

Author: codeMinter

config/development.json

@@ -1,4 +1,4 @@
 {
   "AV_SCAN_SCORER_REVIEW_TYPE_ID": "68c5a381-c8ab-48af-92a7-7a869a4ee6c3",
-  "PROVISIONAL_SCORING_COMPLETED_REVIEW_TYPE_ID": "df51ca7d-fb0a-4147-9569-992fcf5aae48"
+  "PROVISIONAL_SCORING_COMPLETED_REVIEW_TYPE_ID": "52c91e85-745f-4e62-b592-9879a2dfe9fd"
 }

config/production.json

@@ -1,4 +1,4 @@
 {
   "AV_SCAN_SCORER_REVIEW_TYPE_ID": "55bbb17d-aac2-45a6-89c3-a8d102863d05",
-  "PROVISIONAL_SCORING_COMPLETED_REVIEW_TYPE_ID": ""
+  "PROVISIONAL_SCORING_COMPLETED_REVIEW_TYPE_ID": "df51ca7d-fb0a-4147-9569-992fcf5aae48"
 }

src/utils/submission.js

@@ -144,8 +144,9 @@ export function processMMSubmissions(submissions, resources, registrants) {
 
     const provisionalScoringIsCompleted = _.some(
       submission.review,
-      { id: PROVISIONAL_SCORING_COMPLETED_REVIEW_TYPE_ID },
+      { typeId: PROVISIONAL_SCORING_COMPLETED_REVIEW_TYPE_ID },
     );
+
     const provisionalScore = toFixed(_.get(validReviews, '[0].score', '-'), 5);
     const finalScore = toFixed(_.get(submission, 'reviewSummation[0].aggregateScore', '-'), 5);