Support adding completion criteria and validating its structure

[bjester]

Summary

Description of the change(s) you made

• Adds handling for saving completion criteria to node's options
• Updates frontend isNodeComplete logic to validate completion criteria
• Adds new JS dependencies for ajv and kolibri-constants

---

Reviewer guidance

How can a reviewer test these changes?

• Remaining frontend implementation remains a TODO

Are there any risky areas that deserve extra testing?

References

Requires learningequality/le-utils#102

Comments

Frontend isNodeComplete does not validate that certain completion criteria models are only applicable to certain content kinds (model: "pages" <> kind: "audio") Done!

---

Contributor's Checklist

PR process:

• If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
• If this includes an internal dependency change, a link to the diff is provided
• The docs label has been added if this introduces a change that needs to be updated in the user docs?
• If any Python requirements have changed, the updated requirements.txt files also included in this PR
• Opportunities for using Google Analytics here are noted
• Migrations are safe for a large db

Studio-specifc:

• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
• All UI components are LTR and RTL compliant
• Views are organized into pages, components, and layouts directories as described in the docs
• Users' storage used is recalculated properly on any changes to main tree files
• If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

• Code is clean and well-commented
• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Any new interactions have been added to the QA Sheet
• Critical and brittle code paths are covered by unit tests

---

Reviewer's Checklist

This section is for reviewers to fill out.

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
3 Code Smells

No Coverage information
4.9% Duplication

[rtibbles]

I think the only thing left to do here might be to rebase after your duration PR was merged and recreate the migrations accordingly?

[rtibbles]

Woot, good to go!