Fix production task-related issues and issue logging out

[bjester]

Summary

Description of the change(s) you made

• TypeError: find_incomplete_ids() got an unexpected keyword argument 'updated_id' #3931 - fixed regression caused by refactoring of task class in get_node_diff endpoint
• AttributeError: 'UUID' object has no attribute 'encode' #3921 - removed unneeded buggy code that was meant to ensure signature on task result
• IntegrityError: duplicate key value violates unique constraint "django_celery_results_taskresult_task_id_key" #3836 - added retry of saving of task model during enqueue caused by race condition between celery event consumption and enqueue logic
• TypeError: Cannot read properties of undefined (reading 'then') #3925 - always return a promise from sync logic during forced sync at time of signout

Manual verification steps performed

1. Signed in
2. Opened a channel
3. Moved content around
4. Uploaded new file
5. Published channel
6. Signed out

Screenshots (if applicable)

Does this introduce any tech-debt items?

Yes, the changes to resolve the issue with forceServerSync will need refactoring to return a promise that resolves when the sync is actually complete, for the use case of when that function is called during signout. With the upcoming websocket integration, we should be able to resolve it since we're restructuring how we handle data syncing.

---

References

Resolves #3931
Resolves #3921
Resolves #3836
Resolves #3925

Comments

---

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

[rtibbles]

We may be able to use the p-debounce library for this in future, or vendor and modify it like I have here: https://github.com/learningequality/kolibri/blob/develop/kolibri/plugins/learn/assets/src/composables/useProgressTracking.js#L474

[bjester]

Prathamesh and I have been integrating streams into this sync code for websockets, which eliminates this syncActive state management and will make it easier to determine when it's complete.