[feat]: Add common functions for prediction files validation

[vpchung]

Fixes #25

Changelog

• Functions added:

Function Name	Description	Use case
check_missing_keys	Check for missing keys (participant IDs, patient IDs, etc)	There is at least one prediction for every participant / patient / etc.
check_unknown_keys	Check for unknown keys	There are no predictions without a corresponding groundtruth value
check_duplicate_keys	Check for duplicate keys	There is exactly one prediction for a participant / patient / etc.
check_nan_values	Check for NAN values	There are no missing and/or null prediction values
check_binary_values	Check for binary values	Predictions can only be 0 (no disease) or 1 (disease)
check_values_range	Check that values are between min and max values	Prediction values are between the expected range, e.g. probability of disease from 0 to 1, etc.

• Add reference to docs site

Preview

Future work

• Add a tutorial page on how these functions can be used to write a validation script.
• Use Great Expectations SodaCL for validation? As suggested by @thomasyu888

[vpchung]

Any other use cases we should consider? Lmk!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud