[MS-929] Fix 1:N pool count for CoSync

[BurningAXE]

MS-929

Problem
Both the fingerprint and face matcher get the pool size (recorded in OneToManyMatch.MatchPool.count) by calling:
val totalCandidates = enrolmentRecordRepository.count(queryWithSupportedFormat, dataSource = matchParams.biometricDataSource)
This is fine when using the local DB. However, when using CommCare as the biometric data source, we cannot use any of the query’s filtering criteria so instead we just count the whole ContentProvider URI. This means we get the count of all cases in CommCare, regardless of their module or even whether they have biometric data attached or not. This might often lead to incorrect pool size reported in the OneToManyMatch event.

Fix
The fix contains two parts:

1. In the matchers count the number of actually loaded candidates and report that upstream so it ends in the OneToManyMatch event
2. In CommCareIdentityProvider move the onCandidateLoaded callback after filtering so that it only count actually loaded candidates (similar to how the local DB works)

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarQube Cloud