Don't use multiprocessing for downloads.

[rtibbles]

Summary

• A previously unreported regression from Import content issue fixes #9242 would result in errors during content import if worker multiprocessing is used
• Disables use of multiprocessing for file downloads in importcontent
• Does this via a minimal fix to preserve the code paths for future usage and fixing

Reviewer guidance

Run kolibri with the environment variable KOLIBRI_USE_WORKER_MULTIPROCESSING=True ensure that import content works as expected.

---

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

[jredrejo]

Seems logical and harmless