feat: VCVerification API support ARRAY or OBJECT as Credential Sc…

[CryptoKnightIOG]

https://input-output.atlassian.net/browse/ATL-7765

[github-actions]

Unit Test Results

100 files  ±0  100 suites  ±0   18m 26s ⏱️ -30s
860 tests +1  852 ✅ +1  8 💤 ±0  0 ❌ ±0 
867 runs  +1  859 ✅ +1  8 💤 ±0  0 ❌ ±0 

Results for commit 0729ed7. ± Comparison against base commit 6a0a3ea.

♻️ This comment has been updated with latest results.

[github-actions]

Integration Test Results

20 files  ±0  20 suites  ±0   2s ⏱️ ±0s
45 tests ±0  45 ✅ ±0  0 💤 ±0  0 ❌ ±0 
71 runs  ±0  71 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 0729ed7. ± Comparison against base commit 6a0a3ea.

♻️ This comment has been updated with latest results.

[coveralls]

coverage: 49.009% (+0.08%) from 48.925%
when pulling 0729ed7 on ATL-7765
into 6a0a3ea on main.

[mattklepp]

the VcVerificationService handles multiple schemas. The test doesn't check if both schemas were validated. I might be reading it incorrectly.

[CryptoKnightIOG]

the VcVerificationService handles multiple schemas. The test doesn't check if both schemas were validated. I might be reading it incorrectly.

@mattklepp the test parses both Schemas, validates them, then validates the JWT Credentials against both schemas. If either validations fail the test will fails. I know this for a fact because I set "additionalProperties": true in the Schemas them self since both schema check for different properties and was failing otherwise.