MS-124 Use decision policy to determine very good/good/fair matches

[luhmirin-s]

JIRA ticket
Will be released in: 2025.3.0

Notable changes

• Use decision policy to count very good/good/fair matches on the match screen.
• The hardcoded values were kept to have some kind of fallback, but realistically those should never be used.

Testing guidance

• Setup reasonable decision policies per SDK (e.g. 20/50/90 for SimFace).
• Run identifications with known and unknown faces - the amounts of very good/good matches should match the confidence band counts in the result.

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
85.4% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud