Prevent options being a string rather than JSON

[rtibbles]

Summary

Description of the change(s) you made

• Removes an unnecessary json.dumps during publish that was double wrapping the JSON

Manual verification steps performed

1. Wrote a regression test.

Fixes #4141

[bjester]

Looking at the blame history, seems this was a json.dumps for a while? At least since #1896

[bjester]

Kolibri appears to want a text field, not JSON https://github.com/learningequality/kolibri/blob/develop/kolibri/core/content/contentschema/versions/content_schema_current.py#L82

[rtibbles]

When I updated the Kolibri models for use in both kolibri_public and kolibri_content, I also used the Kolibri JSONField implementation (which saves to a text field under the hood): https://github.com/learningequality/kolibri/blob/develop/kolibri/core/content/base_models.py#L133

This was to ensure proper serialization to the API endpoints, but I missed the json.dumps that had previously been used when it had been set as a TextField rather than the JSONField (which handles the json.dumps internally) - so it was getting double json.dumpsed.

[bjester]

Okay that makes sense. Lets make sure that we also QA channel import just in case

[thanksameeelian]

so it was getting double json.dumpsed.

Jason.Jason.Jason.Jason.Jason.Jason.Jason.Jason.Jason.Jason.mp4