Upload bloom format files in studio

[nikkuAg]

Summary

Description of the change(s) you made

I have added the bloompub preset in the contentcuration le-utlis shared folder to allow users to upload bloom files in the studio

Screenshots

References

#4583
#36

Comments

When uploading the bloom file from our PC the File object created on frontend is not able to detect the mimetype of the file and hence sending null to backend in the type property. Should we hardcode it othe front endnd for this format?

---

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 frontend 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]

Let's update to the published le-utils version, and just make sure we're using the code generation script.

[rtibbles]

Seems like these were generated while pointing at your local version of le-utils? Would be good to include the upgrade of le-utils in this PR as well.

[rtibbles]

Did you run this code generation command, or did you do this manually? https://github.com/learningequality/studio/blob/unstable/deploy/generatejsconstantfiles.py

Would be good to run this if not, and commit the results (but make sure to run linting when you do) - just to make sure we've got everything covered.