MS-219 ID pool validation

[luhmirin-s]

Notable changes:

• Added a new step to the identification flow to validate the potential pool of candidates before capturing biometrics.
• If the candidate pool is empty, several conditions are checked to determine the most useful error message. (the error message wording is not final and could be updated via Transifex)
• If the data has not been synced for longer than "maxAge" configuration, the user will be presented with an option to sync and retry.

[alexandr-simprints]

Approving overall, but please address some of the comments

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[BurningAXE]

If the data has not been synced for longer than "maxAge" configuration, the user will be presented with an option to sync and retry.
Can this be named something other than age to avoid confusion (and mixed search results) with subjectAge which is about to be introduced shortly.

[luhmirin-s]

If the data has not been synced for longer than "maxAge" configuration, the user will be presented with an option to sync and retry.
Can this be named something other than age to avoid confusion (and mixed search results) with subjectAge which is about to be introduced shortly.

The name has been discussed and agreed with the cloud team. It will be properly documented to avoid confusion on BE/Vulcan side.