Commit job state change before running update hooks

[dbnicholson]

Summary

Without this, the state queried by job_storage will not match the updated state. This can cause a problem if a hook tries to restart a canceled job because job_storage will still see the state as CANCELING.

Fixes: #11169

References

#11169

This fixes the case I was seeing. Before:

[python-devserver] INFO     2023-08-28 16:22:58,428 Restarting incomplete BackgroundTask func: kolibri_explore_plugin.tasks.remotecontentimport, params: {"channel_id": "2f95235c3709511fa12d007f31ed6a7b", "channel_name": "STEAM", "node_ids": [], "exclude_node_ids": [], "all_thumbnails": true, "fail_on_error": true}, job_id: 3bce247d8c034ea0b694b87f6c2e292c, job_state: CANCELED
[python-devserver] ERROR    2023-08-28 16:22:58,429 exception calling callback for <Future at 0x7f824032a670 state=finished raised JobNotRestartable>

With this change, the job is queued and the server shuts down cleanly.

Reviewer guidance

See the description in #11169. Unfortunately, testing the job worker + StorageHook is not easy.

---

Testing checklist

• 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
• Critical and brittle code paths are covered by unit tests

PR process

• PR has the correct target branch and milestone
• PR has 'needs review' or 'work-in-progress' label
• If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
• If this is an important user-facing change, PR or related issue has a 'changelog' label
• If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

• 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

[github-actions]

Build Artifacts

Asset type	Download link
PEX file	kolibri-0.16.0b4.dev0_git.2.g1e485670.pex
Windows Installer (EXE)	kolibri-0.16.0b4.dev0+git.2.g1e485670-unsigned.exe
Debian Package	kolibri_0.16.0b4.dev0+git.2.g1e485670-0ubuntu1_all.deb
Mac Installer (DMG)	kolibri-0.16.0b4.dev0+git.2.g1e485670-0.3.0.dmg
Android Package (APK)	kolibri-0.16.0b4.dev0+git.2.g1e485670-0.1.0-debug.apk
TAR file	kolibri-0.16.0b4.dev0+git.2.g1e485670.tar.gz
WHL file	kolibri-0.16.0b4.dev0+git.2.g1e485670-py2.py3-none-any.whl

[rtibbles]

I double checked how the hooks are being used in the Android App, and I don't think this should cause any issues. Worth noting that the use case here (manipulating job state within the hooks) was not the original intention of this hook, but I can see why it is useful in this case.