fix: send language updates to the opal-admin backend

[staceybeard]

By submitting this merge request, I confirm the following:

• The merge request title follows the conventional commits convention (see Backend project's README.md)
  • feat: minor app version will be incremented.
  • fix, deps, perf: patch app version will be incremented.
  • chore, ci, etc.: app version will not be incremented.
  • See semantic-release/commit-analyzer
    for complete set of rules.

Changes

Added a call to the Opal-Admin backend API to update the user's language in the Django database.

This will fix deviation warnings in our test data that occur when a test user's language is changed in OpalDB but not in Django.

Dependencies

• Opal-Admin: feat(api): allow caregiver to update their language opal-admin#1926
• Listener: fix: add return code 400 Bad Request opal-listener#605

Issues

Closes #1484

[mschoettle]

Looks good, thanks a lot!

One comment: If there first update fails but the second succeeds we will have a deviation again. Although it is quite unlikely to happen :)

[mschoettle]

Another comment: Are we showing the de option in the app? In that case, would that cause any issues/deviations?

[staceybeard]

Looks good, thanks a lot!

One comment: If there first update fails but the second succeeds we will have a deviation again. Although it is quite unlikely to happen :)

Thanks!

Yes, that's a good point, but probably a rare case. We can fix it manually if it ever happens, probably not worth the effort of adding transactional handling.

Another comment: Are we showing the de option in the app? In that case, would that cause any issues/deviations?

I've fully tested it and both the listener and backend reject the change when given an unsupported language, so it won't create any new deviations. Consistent between both.