Rework evaluation attribute schema validation

[denis-rossati]

Summary

This PR will make the schema validation more robust, very similar to what is done in this part of the evaluation-service

It also increases the maximum amount of characters

• Closes Add a maxLength string validation to the SDK #440

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/@croct/sdk@441

commit: a84b435

[marcospassos]

You don't need this nested function. Is there any reason not to replicate the evaluation service's function?

[denis-rossati]

This is a replica, just a little more verbose because in PHP we can type the array and the associative array at once, here we need to type the array and the object separately

There is one difference, though, that I left out on purpose: the evaluation service's validation allows attributes as arrays like {attributes: [1, 2, 3]}, but here we'll only allow actual objects