Force translations in bulk export/import of user data

[jredrejo]

Summary

After some refactoring in the csv functions, the strings that were translated in the backend were not being translated or serialized in json format when they were still a lazy proxy

This PR:
a) forces all the translation scafolding to be active before calling labeling functions
b) ensures the errors are fully converted to string and not lazy functions before being serialized

References

Closes: #9554

Reviewer guidance

When the server is set to other language different than English check that:
a) Bulk export in the Facility-Data tab works fine, check the exported csv file has its headers translated (if using a language Kolibri supports)
b) Modify the exported csv to introduce error, and import it: It should show the error messages correctly translated in the web UI (while triggering an exception in the server console)
c) tests pass

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

[rtibbles]

Code looks good, if the actions so yes, then so shall we merge!