Upstream sync 1

[Zio-4]

Proposed changes

This is the first upstream sync from the LEVANTE fork. The following changes are included

• Core tasks bumped to version 16. Includes state refactor to be in memory and styling changes for H&F.
• Fix for the dob check which was throwing warnings
• Fixing a typo for the LEVANTE survey "task", survey now saves data regardless if the user responded
• Clearing the game store state on sign out. This was causing an issue when subsequent children were using the same device and seeing the survey as complete from a previous users response.
• German translations for sign page + child view.
• Hiding the SSO logins for admin users (LEVANTE only). We received feedback from our Germany partners that parents / children may get confused and try to use that to sign in. There is a now prompt clearly stating these logins are for admins only.

Types of changes

What types of changes does this pull request introduce?

• [x] Bugfix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] Refactoring (non-breaking change that does not add functionality but makes code cleaner or more efficient)
• [ ] Documentation Update
• [ ] Tests (new or updated tests)
• [ ] Style (changes to code styling)
• [ ] CI (continuous integration changes)
• [ ] Repository Maintenance
• [ ] Other (please describe below)

Checklist

• [x] I have read the guidelines for contributing.
• [x] The changes in this PR are as small as they can be. They represent one and only one fix or enhancement.
• [x] Linting checks pass with my changes.
• [x] Any existing unit tests pass with my changes.
• [x] Any existing end-to-end tests pass with my changes.
• [x] I have added tests that prove my fix is effective or that my feature works.
• [x] If this PR fixes an existing issue, I have added a unit or end-to-end test that will detect if this issue reoccurs.
• [x] I have added JSDoc comments as appropriate.
• [x] I have added the necessary documentation to the roar-docs repository.
• [x] I have shared this PR on the roar-pr-reviews channel (if I have access)
• [x] I have linked relevant issues (if any)

Justification of missing checklist items

Further comments

[richford]

@ksmontville, @lucasxsong, @Emily-ejag, @kellyel: Can one of you explain why the Cypress tests did not run on this PR and what we can do to change that?

[ksmontville]

@ksmontville, @lucasxsong, @Emily-ejag, @kellyel: Can one of you explain why the Cypress tests did not run on this PR and what we can do to change that?

I believe that is is because of the merge conflicts. Any action that is triggered by a pull request will not run if the incoming branch has merge conflicts, according to the docs.

"Notes: Workflows will not run on pull_request activity if the pull request has a merge conflict. The merge conflict must be resolved first."

https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request

GitHub Docs

Events that trigger workflows - GitHub Docs

You can configure your workflows to run when specific activity on GitHub happens, at a scheduled time, or when an event outside of GitHub occurs.