SDK selection based on subject's age

[BurningAXE]

These are the core changes to allow dynamic SDK selection based on age restriction of the SDKs and age of the subject.

Notable parts:

• Use the new project configuration which includes allowedAgeRange for each SDK
• Parse subjectAge from Intent metadata (if present)
• Update StepBuilder to add capture and match steps for appropriate SDKs if they are age restricted and subjectAge is present
• Update StepBuilder to not add capture and match steps for appropriate SDKs if they are age restricted and subjectAge is not present
• Update StepBuilder to add age group selection step if project is age restricted but subjectAge is not present
• Update Orchestrator to add appropriate capture and match steps after age group selection step
• Send 'age group not supported' error if no SDK supports the subject's age
• Update all components that relied on bioSdkConfiguration

Tried to keep commits thematic so the PR can be reviewed commit by commit if you want to follow the logic.

[luhmirin-s]

Is there a reasonable way to avoid hardcoding names?

[BurningAXE]

We don't have anything like a name parameter for SDK config. I can put the names in the resources so they can be reused but this is the first time they appear in UI.

[luhmirin-s]

This line seems to be identical for all flows, could it be moved up the call stack and pre-resolved age be passed in?

[BurningAXE]

The problem is that all 3 functions with repeated code can be called from 2 places (which is why they were extracted in the first place). Was thinking of extracting this part in a helper function but IMO it would hardly improve things - less repetition but more lines of code.

[BurningAXE]

That said - if you can think of a good solution - it's more than welcome!

[ybourgery]

Something that I don't think was discussed in the design document, but with the current implementation the field modalities in the Session is based on the configuration. I think with this work it should be based on the configuration and the actual modalities that we are capturing based on the age.

[BurningAXE]

Something that I don't think was discussed in the design document, but with the current implementation the field modalities in the Session is based on the configuration. I think with this work it should be based on the configuration and the actual modalities that we are capturing based on the age.

Hm, what is this field used for in the backend?

[ybourgery]

Something that I don't think was discussed in the design document, but with the current implementation the field modalities in the Session is based on the configuration. I think with this work it should be based on the configuration and the actual modalities that we are capturing based on the age.

Hm, what is this field used for in the backend?

We use this to know what are the different modalities that are present in the sessions to compute the different metrics/models in Clio

[sonarqubecloud]

Quality Gate passed

Issues
7 New issues
0 Accepted issues

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

See analysis details on SonarCloud